Two separate steps
Deployment puts a new software version where it can run. Release lets users access the changes.
For example, a team could deploy a redesigned checkout to its live site on Tuesday but keep it hidden behind a feature flag. On Thursday, it could release the change to a small group of shoppers, then to everyone.
Why separate them?
This gives the team time for final checks and a planned launch. Before releasing, it confirms which version is running, who will see the change, how to spot problems, and how to respond. Turning off a flag can hide a broken feature, but it cannot undo actions users have already taken.