jsinovassin opened a new pull request, #902:
URL: https://github.com/apache/unomi/pull/902
## Summary
- The `Publish Javadoc and snapshots` workflow on `unomi-3.0.x` runs on a
push to `master` only. The file came from `master` when the branch was cut, and
the trigger was never changed.
- A push to `unomi-3.0.x` therefore deploys nothing. The Apache snapshots
repository holds `3.1.0-SNAPSHOT` and no `3.0.2-SNAPSHOT`, and the branch
received three fixes between 2026-09-28 and 2026-09-30.
- The workflow now runs on a push to `unomi-3.0.x`. A `workflow_dispatch`
trigger is added, so a maintainer can publish the current head without a new
commit.
## Effect on published artifacts
- The Maven snapshots deploy as `3.0.2-SNAPSHOT`, which is the version of
the branch.
- The Docker image is tagged `apache/unomi:${project.version}`, so the job
pushes `apache/unomi:3.0.2-SNAPSHOT` and does not change a `master` tag.
- The Javadoc job generates the aggregate Javadoc and does not publish it to
the site.
## Test
After the merge, run the workflow once from the Actions tab on
`unomi-3.0.x`. Then check that `org/apache/unomi/unomi-bom/3.0.2-SNAPSHOT/`
exists in `https://repository.apache.org/content/groups/snapshots-group`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
