You will probably be okay for the next five to ten years, but I think that after that our programming practices might be so refined that you'll struggle to catch bugs that won't be noticed by the product manager, designer, project manager, scrum master, B.A., and the developers themselves . . . not to mention the 'requirebugs' that customers come up with but a QA engineer would never find, because in a typical fast waterfall environment, they have no interaction with the customer.
Companies that sell automated software tools now state that QA engineers should either learn some form of automation or start thinking about switching to another role that appears in agile environments, such as product manager or scrum master.
A product manager gets to hold that 'subject matter expert' position that many qa engineers enjoy, are essentially writing test cases in the form of requirements, AAANNND . . . you still get to test manually, if you like that sort of thing.
Another interesting role, if you have a technical mindset, is cybersecurity. You may already have many of the skills needed to pursue that growing field.
That being said, I would imagine that for the short term, there will be companies that insist on hands-on testing. The problem that I came across in those roles were:
1) my coworkers expected me to be the SME of ALL the products. And there were a lot of products. Eventually, I couldn't keep up.
2) I felt like I wasn't expanding my knowledge base, while co-workers who did automate increased their skillset and got promoted.
3) Developers, and sometimes everyone else, really expected me to QA literally everything. A database developer accused me of slacking off because he forgot to run a script after a deploy for a specific client. A graphic designer asked me to check the spellings of names on a pamphlet. Clients and client managers confused me for some sort of grouchy customer service intern.
4) Unmaintained, unloved, trashy regression tests written like puzzles (and often floating around for years after the feature was deprecated) made a thorough regression take WEEKS.
5) developers could fix bugs faster than I could write them up.
One thing I would note though, if you decide to stay in QA: keep your skills as well-rounded as possible. Read design blogs, improve your grammar and writing skills, dip into web design for disability accommodation, bone up on Api's, and take a project management class. The manual engineers of tomorrow are going to have a strong knowledge base in all sorts of different fields that are pertinent to computer science.