Conversation
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
publish-releasejob so artifacts are published in one shot.distribution/doc/release-notes/<base-version>.mdviagh release create, replacing the maven-release-plugin commit message that was leaking through before.publish-release; Windows EXE/MSI/ZIP now land in theJSignPdf-<VERSION>/folder on SF alongside the Linux zip, PDF, and README.gh release createcall attaches every asset at once, so repo-watcher emails list the full set.Test plan
Do Releaseworkflow with a test version and confirm the GitHub release body matches the release-notes markdown.frs.sourceforge.net:/home/frs/project/jsignpdf/stable/JSignPdf-<VERSION>/contains both Linux and Windows artifacts.