chore(main): release hve-core 1.1.0#168
Closed
hve-core-release-please[bot] wants to merge 1 commit intomainfrom
Closed
chore(main): release hve-core 1.1.0#168hve-core-release-please[bot] wants to merge 1 commit intomainfrom
hve-core-release-please[bot] wants to merge 1 commit intomainfrom
Conversation
hve-core-release-please
bot
added
the
autorelease: pending
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
WilliamBerryiii
added a commit
that referenced
this pull request
Jan 13, 2026
…rontmatter preservation - add ## 0.0.0 (Initial) placeholder version entry to CHANGELOG.md - ensures release-please updateContent() takes version found path - fixes PR #168 markdown lint failures by preventing frontmatter mangling 🛠️ - Generated by Copilot
WilliamBerryiii
added a commit
that referenced
this pull request
Jan 13, 2026
…rontmatter preservation (#170) ## Summary Fixes #169 Seeds CHANGELOG.md with a placeholder version entry so release-please preserves YAML frontmatter during changelog updates. ## Problem PR #168 fails markdown linting because CHANGELOG.md had no version entry. When release-please's `updateContent()` method runs without a matching version header (`'\n###? v?[0-9[]'`), it takes the "no version found" code path which: 1. Prepends `# Changelog\n` header 2. Adds the new changelog entry 3. Calls `adjustHeaders()` on **all** existing content (including frontmatter) 4. Appends adjusted content at the **end** of the file This mangles the YAML frontmatter, causing MD003, MD012, MD013, and MD022 lint failures. ## Solution Add `## 0.0.0 (Initial)` placeholder version entry. This triggers release-please's "version found" path: ```typescript const lastEntryIndex = content.search(versionHeaderRegex); const before = content.slice(0, lastEntryIndex); // Frontmatter preserved const after = content.slice(lastEntryIndex); // Only versions processed return `${before}\n${this.changelogEntry}\n${adjustHeaders(after)}`; ``` The frontmatter stays in the protected `before` slice and is preserved exactly as-is. ## Changes - [CHANGELOG.md](CHANGELOG.md) - Added `## 0.0.0 (Initial)` placeholder version entry ## Testing - ✅ `npx markdownlint-cli2 CHANGELOG.md` passes with 0 errors ## Next Steps After merging this PR: 1. Close PR #168 2. Release-please will regenerate with the corrected algorithm ## References - [release-please changelog.ts](https://github.com/googleapis/release-please/blob/main/src/updaters/changelog.ts) - `updateContent()` algorithm
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
1 participant
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.
🤖 I have created a release beep boop
1.1.0 (2026-01-13)
✨ Features
🐛 Bug Fixes
📚 Documentation
🔧 Maintenance
This PR was generated with Release Please. See documentation.