Skip to content

chore: release main#352

Open
swernerx wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore: release main#352
swernerx wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@swernerx

@swernerx swernerx commented Jul 6, 2026

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

palamedes: 1.4.0

1.4.0 (2026-07-06)

Features

  • add Remix locale catalog flow (cb111bd)
  • add Remix request i18n scope (aa71708)
  • add Remix v3 register hook (d52e876)
  • benchmarks: model realistic extract-time parse volume (5ec2430)
  • remix: add server API and locale strategy examples (ed1426e)
  • remix: load PO catalogs through node hooks (56d1cc0)
  • site: polish homepage and add realistic 10k-message benchmark (cc47a75)

Bug Fixes

  • address Remix review feedback (18ec453)
  • benchmarks: read multiline PO msgids (a207ed2)
  • remix: address server parity review comments (4ab7db3)
  • satisfy Remix example lint (8ea7741)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Jul 6, 2026

Copy link
Copy Markdown

Greptile Summary

This is an automated release PR generated by Release Please, bumping all packages from 1.3.0 to 1.4.0 across the monorepo. The underlying feature work — Remix locale catalog flow, Remix request i18n scope, and Remix v3 register hook — landed in earlier commits on main and is reflected here only through version and changelog updates.

  • All 24 npm package.json files, 3 Rust Cargo.toml files, Cargo.lock, .release-please-manifest.json, .release-please-version, and CHANGELOG.md are consistently bumped to 1.4.0.
  • No source code logic is changed in this PR; the diff is purely version strings and a new changelog entry.

Confidence Score: 5/5

Safe to merge — all changes are automated version string updates with no logic or source code modifications.

Every changed line is a version bump from 1.3.0 to 1.4.0, applied consistently across all 31 files by Release Please. The CHANGELOG entry accurately reflects the three Remix features and two bug fixes that landed in preceding commits. No source code, configuration logic, or dependency graph was altered.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md New 1.4.0 section added with 3 feature entries and 2 bug fix entries matching the PR description; links are valid commit SHAs.
Cargo.lock Version bumped from 1.3.0 to 1.4.0 for all three Rust packages (palamedes, palamedes-cli, palamedes-node); no dependency changes.
packages/remix/package.json Version bumped to 1.4.0; this package received the new Remix features in the underlying commits.
.release-please-manifest.json Root version updated from 1.3.0 to 1.4.0; consistent with all other version bumps.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] --> B[Detects feat/fix commits on main]
    B --> C[Generates release PR #352]
    C --> D{Version bump 1.3.0 → 1.4.0}
    D --> E[CHANGELOG.md updated]
    D --> F[.release-please-manifest.json]
    D --> G[.release-please-version]
    D --> H[24× package.json files]
    D --> I[3× Cargo.toml files]
    D --> J[Cargo.lock regenerated]
    E & F & G & H & I & J --> K[PR merged to main]
    K --> L[GitHub Release + npm publish triggered]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Release Please Bot] --> B[Detects feat/fix commits on main]
    B --> C[Generates release PR #352]
    C --> D{Version bump 1.3.0 → 1.4.0}
    D --> E[CHANGELOG.md updated]
    D --> F[.release-please-manifest.json]
    D --> G[.release-please-version]
    D --> H[24× package.json files]
    D --> I[3× Cargo.toml files]
    D --> J[Cargo.lock regenerated]
    E & F & G & H & I & J --> K[PR merged to main]
    K --> L[GitHub Release + npm publish triggered]
Loading

Reviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile

@swernerx
swernerx force-pushed the release-please--branches--main branch 2 times, most recently from d0f1738 to 6adeae6 Compare July 6, 2026 21:55
@swernerx
swernerx force-pushed the release-please--branches--main branch from 6adeae6 to 9654807 Compare July 6, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant