I worked as both QA and Release (it was sort of nice to own both sides of the gate) and in some ways that made it easier; in some ways hard. I had a sort of unique situation, though I am sure it exists elsewhere, but I have not encountered many who were doing both sides of the gate like I was. What it will come down it, is the expectation of the QA Role during a release.
Are you there to run the UAT? Because we had the experience, of testing the changes through the QA environment, we knew what to do and what to look for. So the UAT was quick. It also required us less documentation to pass off to the Release Team so they would know what to test, on the odd occasions where a deployment was done by someone else on the team we did have a UAT to run and we also ran other tests knowing that certain parts of a release might touch other systems that we would want to be aware of.
Are you there to assure roll-back? If there is a problem we would have a roll-back plan in place, or in cases when there would be absolutely no way to roll back (those were few and far between) we had to have someone from Dev on hand to help out in case we needed to make changes. Those couple of releases were frightening, such as the 8 hour running cursor with no logging. Considering you mention that your Devs are doing the deploys I suspect you are in a small dev shop and everyone wears many hats, they are familiar with the code and environment so you should have few issues there - one would hope.
Overall you may have an opportunity to define your position here. The fact you are asking may mean they have given you no direction other than you are involved, so determine what your comfort level is and what you will have available to test for updates in production. If you want to test, and be sure, then you need access to Production servers to check logs, events, and other Production level debugging in case there are problems. It can be a good thing overall, QA/RE mixes are rare and if you can do both you bring some very good experience to the table. I've enjoyed it, and I have been comfortable debugging in Production, since I have done it a lot, but also knowing what is needed for hand-off to a RE team is also valuable, since it's different than just putting a package over the wall for someone else.