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
When a managed package is created we currently receive the package name, version and branch if applicable as a line in our sfdx-project.json file. I would LOVE it if the state would also be added when the package is created AND if a package is promoted so we can easily tell which of those packages is beta vs. released. So when the package version promote command is run and a package is updated to released then that item in our sfdx-project.json file is updated with that status...or a new line is added indicating this if update is too difficult.
I know I am constantly running the package version report command on a version to see what the state is.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When a managed package is created we currently receive the package name, version and branch if applicable as a line in our
sfdx-project.jsonfile. I would LOVE it if the state would also be added when the package is created AND if a package is promoted so we can easily tell which of those packages is beta vs. released. So when thepackage version promotecommand is run and a package is updated to released then that item in oursfdx-project.jsonfile is updated with that status...or a new line is added indicating this if update is too difficult.I know I am constantly running the
package version reportcommand on a version to see what the state is.Beta Was this translation helpful? Give feedback.
All reactions