document where to update the stable release now

procedures/foreman/release.md.erb

@@ -151,7 +151,7 @@ Note: If for some reason there was an issue with the tarballs that required uplo
 - [ ] Update the topic in [#theforeman channel on Matrix](https://matrix.to/#/#theforeman:matrix.org)
 - [ ] Share the release announcement on Twitter
 <% if is_first_ga -%>
-- [ ] Update `stable` version in [foreman-infra](https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/profiles/manifests/web.pp#L24)
+- [ ] Update `stable_release` version in [foreman-infra](https://github.com/theforeman/foreman-infra/blob/master/puppet/data/common.yaml#L2)
 - [ ] Create an issue in [foreman-infra](https://github.com/theforeman/foreman-infra/issues) to archive old Debian releases (keeping <%= short_version_minus_five %> and newer)
 <% end -%>
 - [ ] Release pipeline will trigger [foreman-plugins-<%= short_version %>-deb-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-deb-test-pipeline/) and [foreman-plugins-<%= short_version %>-rpm-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-rpm-test-pipeline/). These don't block releases but can be used to understand known issues around plugin compatibility with Foreman <%= short_version %>.