Skip to content

chore: release v1.19.0#361

Merged
jdx merged 1 commit intomainfrom
release
Mar 22, 2026
Merged

chore: release v1.19.0#361
jdx merged 1 commit intomainfrom
release

Conversation

@mise-en-dev
Copy link
Copy Markdown
Collaborator

@mise-en-dev mise-en-dev commented Mar 16, 2026

🚀 Features

  • add reencrypt subcommand for updating encryption recipients by @jdx in #365

🐛 Bug Fixes

  • (set) prompt for secret value when -k flag is used by @jdx in #367

📦️ Dependency Updates

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request prepares for the v1.18.1 release, primarily to reflect recent dependency updates and ensure all version indicators within the project are consistent. It's a maintenance release focused on keeping the project's dependencies current.

Highlights

  • Version Bump: The project version has been incremented to v1.18.1 across all relevant configuration and documentation files.
  • Dependency Updates: This release incorporates recent lock file maintenance, ensuring all dependencies are up-to-date and secure.
Changelog
  • CHANGELOG.md
    • Added a new changelog entry for version 1.18.1, detailing dependency updates.
Activity
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request prepares for the v1.18.1 release by updating the version number in Cargo.toml, Cargo.lock, and various documentation files. It also adds a new entry to CHANGELOG.md. My review found a potential issue with the release date in the changelog.

Comment thread CHANGELOG.md Outdated
@@ -1,5 +1,11 @@
# Changelog

## [1.18.1](https://github.com/jdx/fnox/compare/v1.18.0..v1.18.1) - 2026-03-16
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The release date 2026-03-16 is in the future. Changelog entries are for past events, so using a future date is unconventional and can be confusing. I've noticed this pattern for other releases as well. If this is not an intentional convention for this project, please update it to the actual release date.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 16, 2026

Greptile Summary

This is a standard release PR bumping fnox from v1.18.0 to v1.19.0, aggregating two feature PRs and two dependency-maintenance PRs into a single versioned release.

  • Version string updated consistently across Cargo.toml, Cargo.lock, docs/cli/commands.json, docs/cli/index.md, and fnox.usage.kdl
  • CHANGELOG.md entry added for v1.19.0 documenting the new reencrypt subcommand, the set -k secret-prompting bug fix, and two lock-file maintenance rounds
  • Cargo.lock receives routine dependency bumps: arc-swap, aws-lc-rs/sys, multiple aws-sdk-* crates, itoa, jni-sys (0.3.0 → 0.3.1 + new 0.4.1 split), rustls-webpki, zerocopy, and zune-jpeg — all are patch/minor updates with no breaking changes expected
  • No source code changes are included in this PR; functional changes landed in the referenced feature PRs (feat: add reencrypt subcommand for updating encryption recipients #365, fix(set): prompt for secret value when -k flag is used #367)

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely mechanical release commit with no logic changes.
  • All changes are version-string bumps and lock-file dependency updates. There are no source-code modifications, no new logic, and no risk of regressions. The changelog accurately reflects the two PRs being released. Dependency bumps are all patch or minor level with no known breaking changes.
  • No files require special attention.

Important Files Changed

Filename Overview
Cargo.toml Version bumped from 1.18.0 to 1.19.0; no other changes.
CHANGELOG.md New v1.19.0 section added with feature (reencrypt subcommand), bug fix (set -k prompting), and dependency update entries. Well-formed and consistent with prior entries.
Cargo.lock Lock file updated with routine dependency bumps (arc-swap, aws-lc-rs/sys, aws-sdk-* SDKs, itoa, jni-sys, rustls-webpki, zerocopy, zune-jpeg) plus fnox version bump to 1.19.0.
docs/cli/commands.json Version field updated from 1.18.0 to 1.19.0; no other changes.
docs/cli/index.md Version string updated from 1.18.0 to 1.19.0; no other changes.
fnox.usage.kdl Version field updated from 1.18.0 to 1.19.0; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["PR #365 — reencrypt subcommand"] --> R["Release v1.19.0"]
    B["PR #367 — set -k secret prompting fix"] --> R
    C["PR #360 — lock file maintenance"] --> R
    D["PR #362 — lock file maintenance"] --> R
    R --> V1["Cargo.toml — version 1.19.0"]
    R --> V2["Cargo.lock — dependency updates"]
    R --> V3["docs/cli/commands.json — version 1.19.0"]
    R --> V4["docs/cli/index.md — version 1.19.0"]
    R --> V5["fnox.usage.kdl — version 1.19.0"]
    R --> V6["CHANGELOG.md — v1.19.0 entry"]
Loading

Reviews (4): Last reviewed commit: "chore: release v1.19.0" | Re-trigger Greptile

@mise-en-dev mise-en-dev force-pushed the release branch 2 times, most recently from 82ec5a0 to be25a1d Compare March 22, 2026 22:06
@mise-en-dev mise-en-dev changed the title chore: release v1.18.1 chore: release v1.19.0 Mar 22, 2026
@jdx jdx enabled auto-merge (squash) March 22, 2026 22:27
@jdx jdx merged commit 2e81576 into main Mar 22, 2026
15 checks passed
@jdx jdx deleted the release branch March 22, 2026 22:32
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.

2 participants