Skip to content

Comments

feat(ci): add release-please and improve renovate auto-merge#53

Merged
JacobPEvans merged 2 commits intomainfrom
feat/release-please
Feb 23, 2026
Merged

feat(ci): add release-please and improve renovate auto-merge#53
JacobPEvans merged 2 commits intomainfrom
feat/release-please

Conversation

@JacobPEvans
Copy link
Owner

@JacobPEvans JacobPEvans commented Feb 23, 2026

Summary

  • Adds release-please for automated changelog generation and GitHub releases on merge to main
  • Updates renovate.json to auto-merge actions/* GitHub Actions (matching pattern from ai-assistant-instructions)

Release Please Setup

Modeled after ai-assistant-instructions and ai-workflows:

  • Workflow: minimal, scoped permissions (contents: write, pull-requests: write on job only)
  • Config: simple release type using a VERSION file; changelog shows feat/fix/perf, hides docs/chore/refactor/test/ci
  • Manifest: starts at 1.0.0 (no prior releases)
  • bump-minor-pre-major: true: feat bumps minor while version is < 1.0.0 (not applicable at 1.0.0, but consistent with other repos)

Renovate Update

Added packageRules entry to auto-merge actions/ prefixed GitHub Actions on any version (including major), with squash merge. This covers:

  • actions/checkout
  • actions/setup-python
  • actions/setup-go
  • actions/github-script

Test plan

  • Verify workflow appears in Actions tab after merge
  • Confirm release-please creates a release PR on next feat: or fix: commit to main
  • Confirm renovate auto-merge rule applies to actions/ updates

🤖 Generated with Claude Code


Important

Adds release-please for automated releases and updates renovate.json for auto-merging GitHub Actions.

  • Release Please Setup:
    • Adds release-please.yml for automated changelog generation and GitHub releases on main branch merges.
    • Configures minimal permissions and uses googleapis/release-please-action@v4.
    • Initializes versioning with VERSION file and .release-please-manifest.json starting at 1.0.0.
  • Renovate Update:
    • Updates renovate.json to auto-merge actions/* GitHub Actions with squash merge.
    • Applies to all versions, including major, for actions/checkout, actions/setup-python, actions/setup-go, and actions/github-script.

This description was created by Ellipsis for a0bcbee. You can customize this summary. It will automatically update as commits are pushed.

Add automated release management:
- .github/workflows/release-please.yml: triggers on push to main,
  uses googleapis/release-please-action@v4 with explicit config files
- release-please-config.json: simple release type, VERSION file,
  conventional changelog sections (feat/fix visible, others hidden)
- .release-please-manifest.json: initial version 1.0.0
- VERSION: initial version file at 1.0.0

Update renovate.json to auto-merge official GitHub Actions (actions/* prefix)
on major versions, matching ai-assistant-instructions pattern. This keeps
actions/checkout, actions/setup-python, etc. current without manual PRs.

(claude)
Copilot AI review requested due to automatic review settings February 23, 2026 23:04
@gemini-code-assist
Copy link

Summary of Changes

Hello @JacobPEvans, 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 introduces significant improvements to the repository's continuous integration and dependency management. It sets up automated release processes to streamline versioning and changelog generation, while also enhancing Renovate Bot's capabilities to automatically manage and merge updates for critical GitHub Actions dependencies, ensuring the project stays up-to-date with minimal manual intervention.

Highlights

  • Automated Releases: Integrated release-please to automate changelog generation and GitHub releases upon merging to the main branch, using a simple release type and tracking the version in a dedicated VERSION file.
  • Dependency Automation: Enhanced renovate.json to automatically merge updates for actions/* GitHub Actions, including major version bumps, using a squash merge strategy to keep dependencies current.
Changelog
  • .release-please-manifest.json
    • Initialized the release manifest with version 1.0.0.
  • VERSION
    • Set the initial project version to 1.0.0.
  • release-please-config.json
    • Configured release-please to use a simple release type, track version in VERSION file, enable minor bumps pre-major, and define visible changelog sections.
  • renovate.json
    • Added a new package rule to automatically merge updates for official GitHub Actions, including major versions, using a squash merge strategy.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/release-please.yml
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

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to a0bcbee in 12 seconds. Click for details.
  • Reviewed 61 lines of code in 4 files
  • Skipped 1 files when reviewing.
  • Skipped posting 0 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

Workflow ID: wflow_bykK6BnOjE9lhiXF

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

Copy link

@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 introduces release-please for automated release management and configures Renovate to auto-merge updates for official GitHub Actions. The configuration for release-please is well-structured and follows best practices. For the Renovate configuration, I've suggested a small change to improve safety by adding a delay before auto-merging new releases. Overall, these are great improvements to the repository's CI/CD pipeline.

Provides a 1-day safety buffer before auto-merging GitHub Actions updates,
allowing time for community discovery of supply-chain issues in new releases.
Balances fast updates with stability over null (no delay).

(claude)
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds automated release management via release-please and enhances Renovate's auto-merge capabilities for official GitHub Actions. The implementation follows established patterns from related repositories (ai-assistant-instructions, ai-workflows) with minimal, security-focused configurations.

Changes:

  • Added release-please workflow to automate changelog generation and GitHub releases on pushes to main
  • Configured release-please to use semantic versioning starting at 1.0.0 with a VERSION file
  • Extended renovate.json to auto-merge actions/* GitHub Actions updates (including major versions)

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
.github/workflows/release-please.yml Minimal workflow with scoped permissions (contents: write, pull-requests: write) that triggers release-please on main branch pushes
release-please-config.json Configures simple release type with VERSION file, semantic commit types, and changelog section visibility (shows feat/fix/perf, hides docs/chore/refactor/test/ci)
.release-please-manifest.json Initializes version tracking at 1.0.0 for the root package
VERSION Establishes initial version as 1.0.0 for release-please tracking
renovate.json Adds packageRules to auto-merge actions/* GitHub Actions with squash merge and no minimum release age

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@JacobPEvans JacobPEvans merged commit 94fbaca into main Feb 23, 2026
5 checks passed
@JacobPEvans JacobPEvans deleted the feat/release-please branch February 23, 2026 23:15
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