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, we keep the dist catalog containing all JARs on the main branch, which means that:
it's more problematic for contributors (and me as a maintainer) to make changes because most of them require regenerating the dist directory with a special workflow (or manually)
Renovate cannot automatically merge the PRs
The idea is to generate this directory only for releases. We could have a workflow that is run on main and:
creates a commit with the dist directory, and pushes it
creates a tag with the requested name, and pushes it
creates a GitHub release
The text was updated successfully, but these errors were encountered:
Currently, we keep the
dist
catalog containing all JARs on themain
branch, which means that:dist
directory with a special workflow (or manually)The idea is to generate this directory only for releases. We could have a workflow that is run on
main
and:dist
directory, and pushes itThe text was updated successfully, but these errors were encountered: