Skip to content

Prepare v1.0.1 release#8

Merged
sting8k merged 1 commit into
mainfrom
release/v1.0.1
May 26, 2026
Merged

Prepare v1.0.1 release#8
sting8k merged 1 commit into
mainfrom
release/v1.0.1

Conversation

@sting8k
Copy link
Copy Markdown
Owner

@sting8k sting8k commented May 26, 2026

Summary

  • Bump Cargo, Cargo.lock, and npm wrapper metadata from 1.0.0 to 1.0.1.
  • Move the merged public changes from Unreleased into CHANGELOG.md section 1.0.1 for release-note extraction.

Validation

  • Version consistency check: tag target 1.0.1, Cargo.toml, Cargo.lock package, npm/package.json all match.
  • Changelog extraction smoke for v1.0.1 produced non-empty release notes.
  • git diff --check
  • cargo fmt --check
  • cargo clippy --locked -- -D warnings
  • cargo test --locked
  • cargo build --release --locked
  • npm pack --dry-run in npm/

Release note

This PR only prepares the version bump. Do not tag, publish crates, publish npm, or create a GitHub release until the PR is merged and the final release command is explicitly confirmed.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 26, 2026

Greptile Summary

This PR prepares the v1.0.1 release by synchronizing version metadata across all four relevant files and promoting the accumulated unreleased entries into a dated changelog section.

  • Bumps version from 1.0.01.0.1 consistently in Cargo.toml, Cargo.lock, and npm/package.json.
  • Moves the pending changelog content from the implicit Unreleased block into a new ## [1.0.1] - 2026-05-26 section in CHANGELOG.md, leaving the Unreleased heading in place as a placeholder for future changes.

Confidence Score: 5/5

All four version fields agree at 1.0.1 and the changelog structure is correct; this is safe to merge.

The change is a mechanical version bump across metadata files with no logic, behavior, or dependency changes. All version fields are consistent, the changelog follows the Keep a Changelog convention, and no source code was modified.

No files require special attention.

Important Files Changed

Filename Overview
Cargo.toml Version bumped from 1.0.0 to 1.0.1; consistent with all other version files in this PR.
Cargo.lock srcwalk package version entry updated from 1.0.0 to 1.0.1; only the package version field changed, no dependency graph alterations.
npm/package.json npm wrapper version bumped from 1.0.0 to 1.0.1, matching the Cargo version.
CHANGELOG.md Added [1.0.1] release section dated 2026-05-26 between the empty Unreleased placeholder and the changelog entries, following standard Keep a Changelog format.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR Merged to main] --> B[Tag v1.0.1]
    B --> C1[cargo publish]
    B --> C2[npm publish npm/]
    B --> C3[GitHub Release\ncreated from CHANGELOG]
    C1 --> D[crates.io v1.0.1]
    C2 --> E[npmjs.com srcwalk@1.0.1]
    C3 --> F[Release notes from\nCHANGELOG ## 1.0.1 block]
Loading

Reviews (1): Last reviewed commit: "chore: prepare v1.0.1 release" | Re-trigger Greptile

@sting8k sting8k merged commit 53fbdb4 into main May 26, 2026
3 checks passed
@sting8k sting8k deleted the release/v1.0.1 branch May 26, 2026 09:24
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