antigravity: Update to version 2.0.0, fix checkver & autoupdate

[ghost64]

Fix regex to allow update

Closes #17833

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the Antigravity manifest from 1.23.2 to 2.0.0, replaces Windows x64 and arm64 installer URLs and SHA256 hashes with 2.0.0 release artifacts, and modifies checkver/autoupdate to extract version/build from antigravity-hub/- URLs and to use storage.googleapis.com antigravity-public/antigravity-hub/$version-$matchBuild asset templates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• ScoopInstaller/Extras#16784: Applies similar manifest updates including checkver object restructuring with url, jp, and regex fields alongside versioned asset URL/hash changes.
• ScoopInstaller/Extras#16614: Directly related prior update to bucket/antigravity.json with similar changes to download URLs and checkver parsing.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes the linked issue reference (#17833), confirms the conventional PR title format, and states the Contributing Guide has been read.
Linked Issues check	✅ Passed	The changes directly address the checkver regex issue [#17833] by updating the regex pattern to parse the new antigravity-hub URL format and version scheme.
Out of Scope Changes check	✅ Passed	All changes in the antigravity.json manifest directly support the linked issue objectives: updating to 2.0.0 and fixing the checkver regex.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately reflects the main changes: bumping Antigravity to version 2.0.0 and fixing the checkver regex pattern to parse the new URL structure.

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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[ghost64]

/verify

[github-actions]

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

antigravity

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

Check the full log for details.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

bucket/antigravity.json (1)

51-73: Please run the Scoop manifest checks before merge.

Suggested validation commands:

• .\bin\checkver.ps1 -App antigravity -f
• .\bin\formatjson.ps1 -App antigravity
• scoop install .\bucket\antigravity.json -a 64bit
• scoop install .\bucket\antigravity.json -a arm64

References:

• https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md
• https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests

As per coding guidelines: "[Test Guidance] Provide clear instructions for testing the manifest locally before submission."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/antigravity.json` around lines 51 - 73, Run the Scoop manifest
validation and local install tests for the antigravity manifest: execute the
checkver and formatjson helpers and attempt local installs for both
architectures (use .\bin\checkver.ps1 -App antigravity -f, .\bin\formatjson.ps1
-App antigravity, and scoop install .\bucket\antigravity.json -a 64bit and -a
arm64), then fix any failures in the checkver/autoupdate block—validate the
"checkver" regex and "jp" target, ensure each
autoupdate.architecture.{64bit,arm64}.url is correct and reachable, and confirm
the hash objects point to the correct JSON endpoints and jsonpath
("$.sha256hash"); update "url", "regex", "jp", or "jsonpath" fields in the
manifest accordingly until all validations and local installs succeed.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@bucket/antigravity.json`:
- Around line 53-54: The checkver.regex in the JSON (the "regex" value alongside
"jp": "$.url") doesn't match actual URLs like
.../antigravity-hub/2.0.0-6324554176528384/windows-x64/Antigravity.exe and so
$matchBuild is never captured; update the "regex" field to a pattern that
captures the version and numeric build from that URL format (keep the named
groups (?<version>...) and (?<build>...) so $matchBuild works), e.g. match
"antigravity-hub/{version}-{build}/<platform>/Antigravity.exe" structure and
replace the existing "antigravity-hub/(?<version>[\\d.]+)-(?<build>\\d+)" value
with the corrected regex that includes the trailing slash and platform segment.

---

Nitpick comments:
In `@bucket/antigravity.json`:
- Around line 51-73: Run the Scoop manifest validation and local install tests
for the antigravity manifest: execute the checkver and formatjson helpers and
attempt local installs for both architectures (use .\bin\checkver.ps1 -App
antigravity -f, .\bin\formatjson.ps1 -App antigravity, and scoop install
.\bucket\antigravity.json -a 64bit and -a arm64), then fix any failures in the
checkver/autoupdate block—validate the "checkver" regex and "jp" target, ensure
each autoupdate.architecture.{64bit,arm64}.url is correct and reachable, and
confirm the hash objects point to the correct JSON endpoints and jsonpath
("$.sha256hash"); update "url", "regex", "jp", or "jsonpath" fields in the
manifest accordingly until all validations and local installs succeed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7a6f2abe-453c-460f-bf63-5fa8b4da780a

📥 Commits

Reviewing files that changed from the base of the PR and between 01af506 and dd11a31.

📒 Files selected for processing (1)

• bucket/antigravity.json

[ghost64]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

antigravity

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

Check the full log for details.

[z-Fng]

This will change the package from Antigravity IDE to Antigravity Hub, and the data between the two is incompatible.

[ghost64]

Yeah, I noticed this after making the PR

[z-Fng]

Upgrading to 2.0 and transitioning to Antigravity Hub is the right approach, as it aligns with the standard behavior when installing Antigravity via an installer package, as Google states:

If you already have installed the Antigravity IDE, when that application next updates, it will automatically update to Antigravity 2.0.

The key task here is to notify users of this significant change and fix the extraction method. This is because Antigravity Hub is no longer an Inno Setup installer, but rather NSIS.