chore(dev-docs/ci): update variable names in publish workflows and developer manual to explain CI/CD configurations#2059
Merged
Conversation
…sh workflows - Specify SSH key passphrase using secret variable SOURCEFORGE_KEY_PASS
- Add Continuous Integration and Continuous Delivery (CI/CD) guide. - Update Windows installer tasks and macOS packaging instructions to reflect current Gradle configurations. - Document improved procedures for CI/CD, including sourceforge publishing and notarization. - Fix outdated references to JRE and clarify hardware signing requirements.
miurahr
changed the title
brandelune
reviewed
Jun 1, 2026
miurahr
commented
Jun 2, 2026
Contributor
|
When my note on notarization is finalized we’ll be able to link to it for details. |
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
2 participants
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.
Add CI/CD developer manual section.
Use secret name SOURCEFORGE_KEY_PASS as same as github
Pull request type
Which ticket is resolved?
None
What does this PR change?
Other information