Skip to content

fix(release): move initial-version to root config for all packages - #42

Merged
amondnet merged 1 commit into
mainfrom
fix/release-please-initial-version-root
Mar 13, 2026
Merged

amondnet merged 1 commit into
mainfrom
fix/release-please-initial-version-root

Conversation

@amondnet

@amondnet amondnet commented Mar 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Move initial-version: "0.1.0" from the apps/work-please package-level config to the root config level so it applies globally to all packages.

Why

When Release Please encounters a package at 0.0.0 (never released), it ignores the bump-patch-for-minor-pre-major flag and computes 1.0.0 instead of 0.1.0. Setting initial-version: "0.1.0" at the root ensures the first release starts at 0.1.0 for any package added in the future, not just apps/work-please.


Summary by cubic

Move initial-version: "0.1.0" to the root release-please config so all packages start at 0.1.0 on their first release. This fixes cases where packages at 0.0.0 were computed as 1.0.0 despite bump-patch-for-minor-pre-major.

Written for commit bf447c4. Summary will update on new commits.

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Mar 13, 2026
@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 refactors the Release Please configuration to standardize the initial versioning strategy across all packages. By elevating the initial-version setting to the root level, it guarantees that any package, upon its first release, will consistently begin at 0.1.0, aligning with the intended versioning scheme and avoiding unexpected 1.0.0 bumps for new components.

Highlights

  • Global Initial Versioning: The initial-version: "0.1.0" setting has been moved from the apps/work-please package-level configuration to the root release-please-config.json.
  • Consistent First Releases: This change ensures that all new packages will start their first release at 0.1.0, preventing Release Please from defaulting to 1.0.0 when a package is at 0.0.0 and bump-patch-for-minor-pre-major is enabled.
Changelog
  • release-please-config.json
    • Moved initial-version property from apps/work-please package configuration to the root level.
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. ↩

@dosubot dosubot Bot added the type:bug Something isn't working label Mar 13, 2026
@amondnet
amondnet merged commit 8092154 into main Mar 13, 2026
1 check passed
@amondnet
amondnet deleted the fix/release-please-initial-version-root branch March 13, 2026 03:57

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

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.

Code Review

This pull request correctly adds the initial-version setting to the root of the release-please-config.json to ensure new packages start at version 0.1.0. However, the original package-specific setting was not removed, leading to redundancy. I've added a comment to suggest removing it to complete the intended move and keep the configuration clean.

"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
"bump-minor-pre-major": true,
"bump-patch-for-minor-pre-major": true,
"initial-version": "0.1.0",

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

With initial-version now defined at the root, the package-specific entry in apps/work-please has become redundant. To complete the 'move' as described in the PR summary and keep the configuration clean, please remove the initial-version key from the package configuration.

@cubic-dev-ai cubic-dev-ai Bot left a comment

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.

No issues found across 1 file

Requires human review: CI/CD configuration changes affecting release versioning policy across all packages require human review to ensure alignment with release standards.

amondnet added a commit that referenced this pull request Mar 23, 2026
…efix option

Move git worktrees from <repoDir>/.claude/worktrees/ to
<workspace.root>/github-<owner>-<repo>/worktrees/ to prevent
unstaged changes from blocking before_run hook rebase operations.

Also strip leading # from identifiers (#42 → 42 instead of _42)
and add workspace.branch_prefix config option for custom branch
name prefixes (e.g. agent-please/42).
amondnet added a commit that referenced this pull request Mar 24, 2026
…efix option (#178)

* fix(workspace): move worktree path outside repo dir and add branch prefix option

Move git worktrees from <repoDir>/.claude/worktrees/ to
<workspace.root>/github-<owner>-<repo>/worktrees/ to prevent
unstaged changes from blocking before_run hook rebase operations.

Also strip leading # from identifiers (#42 → 42 instead of _42)
and add workspace.branch_prefix config option for custom branch
name prefixes (e.g. agent-please/42).

* test(workspace): fix applyBranchPrefix test and assert worktree path invariant

- Fix test that claimed to test empty string but passed null
- Add assertion that worktree path uses sanitized identifier (no prefix)

* fix(state): fix ioredis adapter function name and state error tests

- Fix createIORedisState → createIoRedisState to match actual package export
- Mock adapter packages in error tests since they are now installed

* fix(workspace): add branch_prefix to workspace config in test fixtures

* chore: apply AI code review suggestions

- Reuse resolveRepoDir in resolveWorktreePath to reduce duplication
- Assert non-error before checking result.path in test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files. type:bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant