chore(release): set package version to 0.1.15 - Update package.json version from "0.1.15-dev.0" to "0.1.15" to mark a release-ready package. - No other code or dependency changes included.#13
Conversation
added 5 commits
December 24, 2025 18:06
… and logger - Add tests for new error types (CommandError, ArgumentError) and verify Error properties. - Extend GitHub tests with many edge cases and error scenarios: - prompt function behavior and setter - GitHub API error propagation and missing env handling - workflow parsing (invalid YAML, release/push triggers, tag patterns) - issue/PR edge cases (large bodies, title truncation, reuse existing PR, branch mismatch) - milestone-related flows (empty lists, not found, already closed, moving issues) - comment/missing-fields handling and API response robustness - Add comprehensive issue-handling tests: - serialize/deserialize complex issues, category & priority coverage, suggestion lists - formatting/markdown expectations and label checks - behavior when GitHub issue creation fails or returns empty/whitespace responses - enforce fetch limit capping - Augment logger tests: - include vi mocking/cleanup, verify all logger methods, and ensure default console usage behaves as expected - add spies and restore console methods chore: regenerate package-lock.json - Update lockfile (package-lock.json) to reflect dependency resolution / install changes.
- Convert escaped newline/tab/carriage-return sequences (\\n, \\r, \\t) in the release title and body into actual characters before calling octokit.repos.createRelease. - Rationale: release notes produced via JSON serialization or agentic/automated systems can contain literal escaped sequences (e.g. "line1\\nline2"), which GitHub would render as the literal text instead of line breaks. Unescaping ensures multi-line content displays correctly in the release description. - Implementation: added explicit .replace calls to transform common escaped sequences for both title and notes and pass the unescaped values to the GitHub API. - Note: this changes behavior for any release content that intentionally contains literal backslash sequences — those will now be converted to control characters. Adjust tests or callers if they relied on literal escaped sequences.
…file - Update package.json: @eldrforge/git-tools ^0.1.11 -> ^0.1.13 - Regenerate package-lock.json to reflect the new dependency resolution No code changes; lockfile updated to match the dependency bump.
- Update package.json version from "0.1.15-dev.0" to "0.1.15" to mark a release-ready package. - No other code or dependency changes included.
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
ghost
merged commit
This pull request was closed.
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.
Automated release PR.