publishing / versioning single libs

[gipo355]

versioning and publishing strat

what i need:

availability of source code in time

• github release for single packages
• custom assets to github release (war, ng compiled) on every release
• changelog for single packages published in release

release strats available

• independent release

  • independendent package release with independent tags
  • independent changelog

each package will be individually bumped following semver

what happens if app1 is directly linked to lib1 without semver?

angular-tomcat-gradle-monorepo/libs/jakarta-base-rest/build.gradle

Line 20 in a88eb24

implementation project(':libs:smispi')

• sync release

  • sync release (ng style) with single tag

publishing

• multi lang publish (custom pub command?)
• must pub to maven, custom artifactory, npm, etc. (nx command should be easier here)

bump strategy

• automatic continuos release

  • continuous release (auto) on every push (semantic-release strategy)

• choose when to bump

  • rolling open pull request to be merged (changesets strategy)

this could be implemented with a custom action

channels

pre release channels

LTS

will possibly require a release branch to be created on release

---

MENU:

• gh release
• changelog
• independent versioning
• sync versioning
• pre-release
• assets added to release
• pipeline can put in PR
• git tags for sub projects

Libs / Ideas / Strats

• changesets

my preferred strat - allows more control with PR over release timings and content

• gh release
• changelog
• independent versioning
• sync versioning https://github.com/changesets/changesets/blob/main/docs/linked-packages.md
• pre-release https://github.com/changesets/changesets/blob/main/docs/prereleases.md
• assets added to release - nothing found, maybe requires fork and customizing releases
• pipeline can put in PR
• git tags for sub projects - has some quirks, see below

fork and change: changeset cli (publish), changeset action

Tags:
works both with changeset tag and changeset publish but the publish command simply runs npm publish in subproject folder and can't be customized without a fork.

command changeset tag won't tag private packages while changeset publish does - requires a fork maybe?

changeset action with changelog-github creates releases and comments, no customization options to add assets

changeset action can be forked and changed

• nx release

https://nx.dev/features/manage-releases

• gh release - looks like it can't be customized to add assets since it's built into nx? https://nx.dev/recipes/nx-release/automate-github-releases
• changelog
• independent versioning
• sync versioning
• pre-release
• assets added to release - see above
• pipeline can put in PR - must create custom action to apply changes on separate branch and open pr
• git tags for sub projects

The advandate of using nx is that it can be probably customized more having access to independent commands

nx release publish/version/changelog

We can probably write a github action to mirror changesets PRs using it.

can create github releases ( can't customize to add assets )

creates tags for every subproject.

Must test sync strat with it and see if it generates one root changelog, if it creates sub proj tags.

how to add assets to each?

must customize github release to add wars etc

https://nx.dev/recipes/nx-release/automate-github-releases

check https://github.com/nrwl/nx/blob/master/nx.json

• semantic-release

doesn't work for monorepo?

• jscutlery plugin

could possibly became a mess? this level of automation for a monorepo is probably not feasable

creates releases using gh cli. possibly use this method to create custom pipeline?

• release-please

notes

i can use package.json to version single libs. gradle can parse the file to set it

can customize changesets publish commands

can use nx release publish to publish individual libs.

can customize nx release publish command maybe to implement gradle publish.

gradle publish need to take into account the package.json version to set the -Pversion of the individual lib

we don't have access to tags for individual libs?

but i need to create a tag for lib/release and add the assets

grouped libs may be bumped together following angular style