Add @since to release checklist

.github/pull_request_template.md

@@ -30,7 +30,8 @@ This PR bumps the version to <version number>.
 1. Look at the [CHANGELOG.md](../CHANGELOG.md) to determine whether the release should be a major, minor, or patch release. Coordinate with the team to ensure the next version is agreed upon.
 2. Run `npm version -- <major|minor|patch> --no-push` with the decided on version (to prevent the tag from being pushed).
 3. Update the `CHANGELOG.md` to release the latest the version, and set the release date.
-4. Commit the changes on a `release/vX.Y.Z` branch
-5. Push to GitHub, create a PR, and merge once CI passes.
-6. Create a release on GitHub for the new version, using a combination of the release notes from the `CHANGELOG.md` and the automatically generated changes.
+4. Add the `@since X.Y.Z` annotations to new APIs.
+5. Commit the changes on a `release/vX.Y.Z` branch
+6. Push to GitHub, create a PR, and merge once CI passes.
+7. Create a release on GitHub for the new version, using a combination of the release notes from the `CHANGELOG.md` and the automatically generated changes.
    The release should have a new tag matching the new version number: `vx.y.z`, and point to the release commit.