Repository navigation
Conversation
fateeand
requested review from
TerranceKhumalo-absa,
korel-san and
lukasmatta
as code owners
November 11, 2026 13:22
Contributor
Ngx coverage report
Test suite run success544 tests passing in 14 suites. Report generated by 🧪jest coverage report action from 1abc4fb |
Contributor
Core coverage report
Test suite run success419 tests passing in 22 suites. Report generated by 🧪jest coverage report action from 1abc4fb |
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part 8 of 8 of the split of #34. It releases and publishes the two packages, independently versioned, and updates the docs and logos. It is the only
feat:in the series, so the core's first release (0.1.0) happens here.Changes
^the new core. The core starts at0.1.0; the adapter continues from 0.4.0. Tags becomeui-watchtower-v…andngx-ui-watchtower-v….scripts/publish-packages.mjspublishes what was released, the core before the adapter. It skips versions npm already has and stops before the adapter if the core fails, so rerunning finishes a partial release.release:checkreplays Release Please on the config.docs/ADAPTERS.md(writing an adapter for another framework), and the logos for light and dark.Before merging the release PR
npm sets up trusted publishing only for a package that exists. Before merging the release PR, an
@absaoss-cpsowner publishes the core at0.1.0once by hand, then adds its trusted publisher (GitHub Actions,AbsaOSS/ui-watchtower, workflowrelease-please.yml). The README's "Releases" section has the exact commands.Closes #44
Part 8 of 8 of the epic #35. Stack on GitHub, merged bottom first: