A workflow without subtree split

What if we used a config JSON at the root of the repository that contained the path to the package.json file, so that we no longer need it to be at the root of the repository?

Then after cloning, we can simply use the folder containing the package.json as the UPM package.

This way we wouldn’t need to maintain a separate branch just for UPM releases.

What do you think? Is this feasible, or even possible?

[mob-sakai]

Sorry my late reply.

git-upm-publisher is a good idea. 😃 I am delighted to be able to release it on the command line. Currently, I am working on automatic release support via semantic-release. It generates a changelog, publishes it to any npm registry (option), and updates the upm branch.

Aside from that, I came up with a way to install subdirectory packages. It is not yet ready for release, but it may fulfill your wishes. 😃

[mob-sakai]

@starikcetin I use this: https://www.npmjs.com/package/git-snapshot

I want a simpler release workflow…

• Changelog: Generate based on commit message, not Github issues.
  • https://github.com/conventional-changelog/conventional-changelog
• Versioning: Automatically, not manually
• Portability: Just execute npm run release
• Release: Tag and squashed-split to upm branch and release on Github