Repository navigation
release: prepare Doc2FAQ v0.3.1 with neutral Q&A examples - #9
Merged
Merged
Conversation
Set the Maven version to 0.3.1, finalize the changelog, document rebuilding and publishing the matching JAR, and replace payment examples with neutral Q&A and team knowledge content.
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.
Prepare v0.3.1 so the next runnable JAR includes the parsing, stale-draft, and responsibility-deduplication fixes already merged in #8.
0.3.1and finalize the changelog.doc2faq-0.3.1.jarfrom the matching release commit.Validation:
mvn -B -ntp clean verify: 38 Java tests passed; runnable v0.3.1 JAR built successfully.node --test src/test/js/*.test.cjs: 12 JavaScript tests passed.After merging: pull the release commit, rebuild and smoke-test the JAR, then create tag
v0.3.1and attachtarget/doc2faq-0.3.1.jarto the new GitHub Release. This PR does not publish a release or replace the existing v0.3.0 artifact.