docs: update README for Node-based build and automated releases#192
Merged
Conversation
- Update build instructions to Node.js / npm (the Maven flow was removed in eXist-db#183) - Fix CI badge URL/name (workflow renamed ci.yml -> build.yml) - Add Release Procedure section documenting the semantic-release flow, required conventional-commit format, and what contributors / release managers need to do - Tidy installation and dependency wording Closes eXist-db#191
duncdrum
approved these changes
May 27, 2026
|
🎉 This PR is included in version 3.0.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
[This response was co-authored with Claude Code. -Joe]
Closes #191.
The README still documented the old Maven flow after #183 landed. Updates:
ci.yml→build.ymlin feat!: de-mavenize the build #183, so the existing badge was 404ing on masterThis was originally intended as part of #183 but didn't make it in before the merge — opening as a standalone follow-up.