Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Support .NEXT for Source/Data Packages #1065

Closed
azlam-abdulsalam opened this issue Jun 19, 2022 · 0 comments · Fixed by #1080
Closed

Support .NEXT for Source/Data Packages #1065

azlam-abdulsalam opened this issue Jun 19, 2022 · 0 comments · Fixed by #1080
Assignees
@azlam-abdulsalam @zhebinliu
Labels
enhancement enhancement to existing feature
Milestone
Release July - 2022

Comments

@azlam-abdulsalam
Copy link
Contributor

sfpowerscripts should support .NEXT for source and data package, As salesforce is not aware of the package creation for these types, it would not be possible for sfpowerscripts to implement an equivalent operation to .NEXT, it would be still beneficial from a developer experience perspective, to automatically strip NEXT and replace it with build number if provided or use a guid
@azlam-abdulsalam azlam-abdulsalam added the enhancement enhancement to existing feature label Jun 19, 2022
@azlam-abdulsalam azlam-abdulsalam added this to the Release July - 2022 milestone Jun 19, 2022
@azlam-abdulsalam azlam-abdulsalam self-assigned this Jun 19, 2022
@github-actions github-actions bot added the analysis To be decided on how to solution/fix label Jun 19, 2022
azlam-abdulsalam pushed a commit that referenced this issue Jul 11, 2022
feat(package-build): allow .NEXT in source/data packages
ab9c359 
This allows for creating packages with .NEXT in source and data packages, by simply substituting
with buildnumber. Also deprecate increment package version number functionality as a proper
implementation is available in sfp-cli

BREAKING CHANGE: Deprecates package:version:increment command, Breaking changes in core

fixes #1065
@azlam-abdulsalam azlam-abdulsalam linked a pull request Jul 11, 2022 that will close this issue
feat(package-build): allow .NEXT in source/data packages #1080
Merged
5 tasks
@azlam-abdulsalam azlam-abdulsalam mentioned this issue Jul 11, 2022
Merged
5 tasks
azlam-abdulsalam pushed a commit that referenced this issue Jul 14, 2022
feat(package-build): allow .NEXT in source/data packages
04cf1f2 
This allows for creating packages with .NEXT in source and data packages, by simply substituting
with buildnumber. Also deprecate increment package version number functionality as a proper
implementation is available in sfp-cli

BREAKING CHANGE: Deprecates package:version:increment command, Breaking changes in core

fixes #1065
azlam-abdulsalam added a commit that referenced this issue Jul 14, 2022
@azlam-abdulsalam
feat(package-build): allow .NEXT in source/data packages (#1080)
45fc0e2 
* feat(package-build): allow .NEXT in source/data packages

This allows for creating packages with .NEXT in source and data packages, by simply substituting
with buildnumber. Also deprecate increment package version number functionality as a proper
implementation is available in sfp-cli

BREAKING CHANGE: Deprecates package:version:increment command, Breaking changes in core

fixes #1065
@azlam-abdulsalam azlam-abdulsalam removed the analysis To be decided on how to solution/fix label Jul 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@azlam-abdulsalam azlam-abdulsalam

@zhebinliu zhebinliu

Labels
enhancement enhancement to existing feature
Projects
None yet
Milestone
Release July - 2022
Development

Successfully merging a pull request may close this issue.

feat(package-build): allow .NEXT in source/data packages dxatscale/sfpowerscripts
2 participants
@azlam-abdulsalam @zhebinliu