Skip to content

Publish jar to GitHub Packages#2

Open
forus wants to merge 3 commits intomainfrom
publish-jar-to-gh-artifact-storage
Open

Publish jar to GitHub Packages#2
forus wants to merge 3 commits intomainfrom
publish-jar-to-gh-artifact-storage

Conversation

@forus
Copy link

@forus forus commented Mar 16, 2026

No description provided.

@forus forus force-pushed the publish-jar-to-gh-artifact-storage branch from d90475a to 3f2f7ad Compare March 16, 2026 12:52
@forus forus force-pushed the publish-jar-to-gh-artifact-storage branch from 3f2f7ad to 3ed031e Compare March 16, 2026 13:03
@forus forus changed the title Publish jar to GitHub artifact storage Publish jar to GitHub Packages Mar 16, 2026
Drop the optional dependency snapshot submission step from the Maven
workflow. It fails with `403 Resource not accessible by integration`
and relies on deprecated `set-output`.

Prefer these alternatives instead:
- enable GitHub automatic dependency submission in repository settings
- keep CI limited to build and publish steps

Shorter version:

ci: remove outdated dependency submission step

The action fails in PR contexts with 403 and uses deprecated output
handling. Use GitHub automatic dependency submission instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant