Backport package.json to master branch
See original GitHub issueHi @DanielEverland,
Thanks for creating the awesome package. I work on https://github.com/openupm/openupm, which is an upcoming UPM registry for open source unity package (sneak preview). The service can build and publish UPM package direcly from git repo. For ScriptableObject-Architecture, however certain changes are required
- backport package.json from stable branch to master, located at Assets/So Architecture.
- stick to semver, where 1.6.2.1 is not a valid semver, but 1.6.3 is. I noticed it get corrected in later commit.
- make a new release 1.6.3.
The openupm build pipeline will checkout each tags that is valid semver, and locate the package.json file as the root, then run npm publish
from there.
The changes benefit openupm, but are good practice in general.
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
backport
How it works. Select a commit to backport; Select a branch to backport to; The commit will be cherrypicked, pushed and a pull...
Read more >Package.json with GIT Workflow - Separate dependency ...
I am using GIT Workflow (develop, master, feature, release) branches for our software development. Now our software has few internal dependents ...
Read more >github-backport | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >how to maintain two major versions at the same time? #371
Y branches (in case one wants to backport bugfixes to multiple minor ... Create branch 3x from master; Change the package.json on branch...
Read more >Use Github branch as dependency in package.json
json dependencies using the username/repo#branch-name format. Run npm install and npm will download the project and save it into your /node_modules/ folder.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sounds great, thanks for the effort. I will close this issue for now. But feel free to use this conversation to notify me about the coming 1.6.4 release.
Makes sense. Next release is 1.6.4, I’ll ping you when it’s done, just to make sure everything’s working as-intended 😃