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
Currently, all packages have their own versions system. This discrepancy creates many problematic situations in the cases of reporting issues and managing their versions. I'm curious to improve this process and made it automatic and uniform for all packages. That would be wonderful :)
TODO:
At first, uniform versions. All packages should have introduced uniform versions, same for all packages. That will be much easier to manage. Also, on the client user's (developer's) side, using packages in the same version guaranty all work perfectly together.
Secondly, one for all. One script should work for all. It should be placed in the main package.json. Then run npm version & npm publish for all packages. That makes publishing a new version much more convenient. Probably the workspace feature will work great for that point.
Then, develop branch. As this script will run automatically, it is required to introduce the develop, because I want to release new versions too often (that will be annoying for developers using our packages). So, all changes go into feature branches, then merged into the develop. Then not often than once a week, I will create PR into master, merge and release a new version.
Workflow: PR into master, a workflow scheduled once a week to check and create a PR from developing into master, and earlier bumping a version. To consider how to detect the level of the incremented version (patch or minor).
Workflow: publish version, workflow started when pushed into the master branch. Publish version into npm, and (proposal:) report it in social media (fi. twitter/linkedin/fb/dev.to/hn)
The text was updated successfully, but these errors were encountered:
Continues Delivery
Currently, all packages have their own versions system. This discrepancy creates many problematic situations in the cases of reporting issues and managing their versions. I'm curious to improve this process and made it automatic and uniform for all packages. That would be wonderful :)
TODO:
npm version & npm publish
for all packages. That makes publishing a new version much more convenient. Probably the workspace feature will work great for that point.develop
branch. As this script will run automatically, it is required to introduce thedevelop
, because I want to release new versions too often (that will be annoying for developers using our packages). So, all changes go into feature branches, then merged into thedevelop
. Then not often than once a week, I will create PR intomaster
, merge and release a new version.The text was updated successfully, but these errors were encountered: