- 
                Notifications
    You must be signed in to change notification settings 
- Fork 31
Release Process
        Jen Basch edited this page Oct 3, 2025 
        ·
        8 revisions
      
    - Add release notes to docs/modules/ROOT/pages/CHANGELOG.adoc
- Change version in docs/antora.yml
- Change version in docs/modules/ROOT/partials/component-attributes.adoc
- Change version in VERSION.txt
- Commit message: "Prepare x.y.z release"
- Submit PR and merge approved PR into the main branch
- 
If a new minor version, create a release branch - git checkout -b release/x.x
- push to origin
 
- 
Otherwise, merge changes into release branch - git checkout release/x.x
- git merge --ff-only main
- push to origin
 
- 
Commit and create a tag. Make sure the tag does not have a "v" prefix. git tag -a x.y.z -m "Release version x.y.z"
- 
Push to apple/pkl-swift These instructions assume that the apple/pkl-swift remote is called "upstream". git push upstream refs/tags/x.y.z
- 
Wait for CI job to finish