Skip to content

Latest commit

 

History

History
60 lines (46 loc) · 4.43 KB

File metadata and controls

60 lines (46 loc) · 4.43 KB

Release process

Branches

The primary working branch for this repo is the main branch. This branch tracks the in-development branch of core. The patch branches are named 252-patch and such. The patch branches track the production branches of core. A new patch branch is created at Code Line Cut Over(CLCO).

Any bug fixes targeted for production should be first committed to the main branch and then backported to the appropriate patch branch.

Versioning

This repo has been setup to release using githooks. Any PR merged to main branch will be immediately released and tagged as next. For the patch branches, the tag is either latest or prerelease based on the configuration in the onRelease github hook. The latest tag is used for the patch branch tracking the production branches of core.

The Salesforce release is deployed in a staggered manner. There is a phase where the upcoming production release is available on Sandboxes as a preview to customers. Such customers can use the prerelease version of the plugin. At CLCO, the new patch branch will be set to release with prerelease tag. After R2b release, the prerelease version will be promoted to be the latest by modifying the onRelease github hook.

Example Flow

See release calendar in GUS for exact dates.

CLCO (Feature Freeze)

  • Merge any outstanding PRs to main
  • Create a new *-patch branch based on main once CI has published to NPM.
  • Create a main branch pull request. NOTE: PR details must have "BREAKING CHANGE" in the description. Once merged and CI is complete, ensure a new major version (i.e. 3.x.x -> 4.0.0) of the plugin has been published to NPM with the "next" tag.
  • If the release to NPM doesn't happen, you can manually run a release via Github actions or by submitting a release PR.
  • Create a patch branch pull request on the *-patch branch to release the pre-release version of the plugin. Ensure this step completes successfully and has released a newly tagged "prerelease" version of the plugin to NPM.

R2b Release

  • Create a patch branch pull request.
  • Ensure this step completes successfully and has released a newly tagged "latest" version of the plugin to NPM.

Branch / Release / API Version Reference

Core Branch Release Name API Version Plugin Version
252-patch winter25 62 1
254-patch spring25 63 2
256-patch summer25 64 3
258-patch winter26 65 4
260-patch spring26 66 5
262-patch summer26 67 6
264-patch winter27 68 7
266-patch spring27 69 8
268-patch summer27 70 9
270-patch winter28 71 10
272-patch spring28 72 11
274-patch summer28 73 12
276-patch winter29 74 13
278-patch spring29 75 14
280-patch summer29 76 15
282-patch winter30 77 16
284-patch spring30 78 17
286-patch summer30 79 18
288-patch winter31 80 19
290-patch spring31 81 20
292-patch summer31 82 21
294-patch winter32 83 22
296-patch spring32 84 23
298-patch summer32 85 24
300-patch winter33 86 25