Skip to main content
Salesforce

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    ohhh thank you for advising me. Sound like I need to research and integrate versioning in workflow to enhance it Thank you so much, I appreciate it Commented Oct 26, 2023 at 6:20
  • @vctqs1 : Yes , having CI/CD helps in release process. 2GP is more friendly from CI/CD perspective. Commented Oct 26, 2023 at 6:27
  • Also, having question from me. As I searched, the patch update also limit in some specific changes. so in that case. we should provide a minor instead, is it? Also w patch update, we dont need do promote version. right? How about if I increase build in major.minior.patch.build? Do it work? Commented Oct 26, 2023 at 6:34
  • If by promotion you mean listing on appExchange or using on production , it is optional to promote major/patch version.Also , I doubt we can have numbering like major.minior.patch.build for 1GP package. Also , the last number is always the patch number. It can't be build number. For 2GP , this doc gives some insights. Commented Oct 26, 2023 at 6:52
  • ohmm about creating new version number, I'd like to do something automation on CI/CD, there are any ways or cli, that able to auto-detect the changes and create correctly version number with patch or minor or major? something like this? Commented Oct 26, 2023 at 7:27