Conversation
| } | ||
|
|
||
| # Read xml and assign Manifest API value | ||
| while read_package; do |
There was a problem hiding this comment.
why even bother reading the current versions and comparing them with the latest?
Seems much simpler to just blind write the newest version every time, and the outcome is effectively the same.
There was a problem hiding this comment.
less editing of the files was my thought.
- Catching up with master to avoid conflicts and for testing
|
@ChuckJonas seems like a perfect time to merge this and package it up since our image is out of date. I can merge but am not sure how to package it for npm ( I think you have a specific user/pwd for that?).
|
|
@fishygeek91 i'd love to broaden out pushing updates to our npm projects. perhaps you could work with charlie to set things up? key goals, reducing charlie bus factor, easy management of team members who can push items, and the ability to scope package visibility to public or just team members. i know npm has "teams" and "organizations" but I'm not sure if they're paid things, it's probably worth it at low rates. |
3 participants
Script retrieves the latest version from the source org and updates the project manifest and sfdx-project json file.
Testing took a long time as the jq and sed tools were different for the CI shell in bitbucket, and I had to find some work arounds for each.
@ChuckJonas @ralphcallaway if you have any suggestions for improvements, I'm all ears