Repository navigation
Release management: automatically tag @since annotations with the correct version #151
Closed as not planned
Description
As of SCF 6.4, every time we add a new APi, we need to manually add the specific version @since annotation, which can lead to inaccuracies: if there is a new release before the branch with the new API is merged, its @since annotations need to be updated.
SCF should have a placeholder like {NEXT_MAJOR_VERSION} that gets replaced with the appropriate version during the release process jobs, so that contributors just need to type @since {NEXT_MAJOR_VERSION}.
Activity
cbravobernal commentedon Oct 27, 2026
Closing this.
@sinceversions are set or checked on the release branch during release prep, by hand or with help from an AI tool, so we won't add a placeholder that's replaced automatically. See #547 for the discussion.