You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
sfpowerscripts in its current design, implies that promoted packages have to be republished (as it internally changes the artifact state to mark it as promoted). This would only work when the user is having two artifact registries.If its a single artifact repo such as npm is used, the package gets rejected, if its already published (say from trunk). This implies that the packages have to be rebuilt when a release branch is cut.
To enable it the following should be done
The promote flag should be removed from the internal state
Promotion should be moved into the release definition where packages are promoted before deploying to a particular environment
The text was updated successfully, but these errors were encountered:
Have Raised a PR for fixing this. Release command will have an option to promote packages before installing into an org.
The sequence will be Promote and Install, thus allowing development team to fix only the package that they failed to promote, rather than incrementing all the packages again.
sfpowerscripts in its current design, implies that promoted packages have to be republished (as it internally changes the artifact state to mark it as promoted). This would only work when the user is having two artifact registries.If its a single artifact repo such as npm is used, the package gets rejected, if its already published (say from trunk). This implies that the packages have to be rebuilt when a release branch is cut.
To enable it the following should be done
The text was updated successfully, but these errors were encountered: