Skip to content

Fixed packages name conversion in migration script#2144

Merged
kvaps merged 1 commit intomainfrom
fix/migration-script
Mar 3, 2026
Merged

Fixed packages name conversion in migration script#2144
kvaps merged 1 commit intomainfrom
fix/migration-script

Conversation

@myasnikovdaniil
Copy link
Contributor

@myasnikovdaniil myasnikovdaniil commented Mar 3, 2026

What this PR does

Release note

Fixed migrate-to-version-1.0.sh script to properly convert packages names.

Summary by CodeRabbit

  • Chores
    • Updated migration tooling to improve package configuration handling during version upgrades.

@dosubot dosubot bot added size:XS This PR changes 0-9 lines, ignoring generated files. bug Something isn't working labels Mar 3, 2026
@gemini-code-assist
Copy link
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 resolves an issue in the migrate-to-version-1.0.sh script that prevented correct package name conversion. The changes ensure that package names are consistently prefixed with "cozystack." when bundles are enabled or disabled, thereby preventing potential configuration errors during the migration process.

Highlights

  • Package Name Conversion: The migration script migrate-to-version-1.0.sh has been updated to correctly prepend the "cozystack." prefix to package names when processing BUNDLE_DISABLE and BUNDLE_ENABLE environment variables. This ensures proper formatting for bundle configurations.
  • Script Formatting Cleanup: A minor whitespace inconsistency was resolved in the migrate-to-version-1.0.sh script, specifically removing a trailing space from an if condition related to the BRANDING variable.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • hack/migrate-to-version-1.0.sh
    • Corrected the awk command to prepend "cozystack." to package names when handling BUNDLE_DISABLE.
    • Corrected the awk command to prepend "cozystack." to package names when handling BUNDLE_ENABLE.
    • Removed a trailing space from an if condition related to the BRANDING variable for minor code cleanup.
Activity
  • No specific activity (comments, reviews, or progress updates) has been recorded for this pull request since its creation.
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.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 3, 2026

📝 Walkthrough

Walkthrough

A migration script is updated to prefix items in comma-separated lists with "cozystack." when converting them to YAML arrays for both disabledPackages and enabledPackages fields during the version 1.0 migration process.

Changes

Cohort / File(s) Summary
Migration Script Update
hack/migrate-to-version-1.0.sh
Modified YAML array conversion logic to add "cozystack." prefix to package names in disabledPackages and enabledPackages lists.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A script hops along with newfound care,
Each package name now wears a cozystack flair,
Three lines of wisdom, prefix in place,
Migration dancing at a quicker pace! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing package name conversion in the migration script, which matches the AI-generated summary and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/migration-script

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
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 fixes the package name conversion in the migration script by adding the cozystack. prefix, which is correct. I've also provided suggestions to fix a minor issue in the awk commands that generate an extra newline, to ensure cleaner output.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@hack/migrate-to-version-1.0.sh`:
- Around line 158-164: The package-list conversion for DISABLED_PACKAGES and
ENABLED_PACKAGES blindly prepends "cozystack." to every token and doesn't trim
or skip empty tokens; update the conversion logic used for BUNDLE_DISABLE and
BUNDLE_ENABLE so it: splits on commas, trims whitespace from each token, skips
empty tokens, and only prepends "cozystack." when the token does not already
start with that prefix (preserve tokens that already include it). Locate the
conversion expressions that set DISABLED_PACKAGES and ENABLED_PACKAGES and
change their sed/awk pipeline (or replace with a small POSIX shell loop) to
perform trimming, empty-token filtering, and conditional prefixing before
emitting the "          - cozystack.<pkg>" list entries.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 772fb43 and 780af33.

📒 Files selected for processing (1)
  • hack/migrate-to-version-1.0.sh

@kvaps kvaps added the backport Should change be backported on previus release label Mar 3, 2026
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Mar 3, 2026
@kvaps kvaps merged commit f5b29e1 into main Mar 3, 2026
15 of 16 checks passed
@kvaps kvaps deleted the fix/migration-script branch March 3, 2026 23:22
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

Successfully created backport PR for release-1.0:

kvaps added a commit that referenced this pull request Mar 5, 2026
…ript (#2148)

# Description
Backport of #2144 to `release-1.0`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Should change be backported on previus release bug Something isn't working lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants