Skip to content

release: prepare Doc2FAQ v0.3.1 with neutral Q&A examples - #9

Merged
OKAN-SOFTWARE merged 1 commit into
mainfrom
release/doc2faq-v0.3.1
Oct 26, 2026
Merged

OKAN-SOFTWARE merged 1 commit into
mainfrom
release/doc2faq-v0.3.1

Conversation

@OKAN-SOFTWARE

Copy link
Copy Markdown
Owner

Prepare v0.3.1 so the next runnable JAR includes the parsing, stale-draft, and responsibility-deduplication fixes already merged in #8.

  • Set the project version to 0.3.1 and finalize the changelog.
  • Replace the document-content placeholder with neutral Q&A about organizing notes and writing useful answers.
  • Replace the Generate Mode payment/agreement sample with a team knowledge guide and update the README example.
  • Document building, restarting, occupied ports, and publishing the tested doc2faq-0.3.1.jar from 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.
  • Additional DOM checks passed for editing, reordering, search, imports, exports, escaping, and stale-response handling.
  • Verified the JAR manifest and startup report v0.3.1 and the bundled frontend matches the updated source.
  • Packaged-app API checks extracted both placeholder Q&A pairs, generated four FAQs from the new team sample, and retained separate client/provider responsibilities.
  • Confirmed payment and fee examples are absent from the interface placeholder and loaded samples.

After merging: pull the release commit, rebuild and smoke-test the JAR, then create tag v0.3.1 and attach target/doc2faq-0.3.1.jar to the new GitHub Release. This PR does not publish a release or replace the existing v0.3.0 artifact.

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.
@OKAN-SOFTWARE
OKAN-SOFTWARE merged commit 59696c1 into main Oct 26, 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