Skip to content

fix(ci): derive GPG verification paths from Maven version - #37

Merged
maxim618 merged 1 commit into
mainfrom
fix/gpg-signing-project-version
Oct 5, 2026
Merged

maxim618 merged 1 commit into
mainfrom
fix/gpg-signing-project-version

Conversation

@maxim618

@maxim618 maxim618 commented Oct 5, 2026

Copy link
Copy Markdown
Owner

What changed

  • derive the project version from Maven in the gpg-signing job
  • verify the JAR, sources JAR, Javadoc JAR, and POM signatures using that version
  • remove hardcoded 0.1.0-SNAPSHOT artifact paths

Why

The project was released as 0.1.0, but the CI signature verification step still looked for 0.1.0-SNAPSHOT artifacts, causing the gpg-signing job to fail after the release preparation was merged.

This keeps the workflow independent of the current project version.

@maxim618
maxim618 merged commit b7ac8ac into main Oct 5, 2026
2 checks passed
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