Update roblox-creator-docs extension

[pernielsentikaer]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @choppedtuna you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="ext/roblox-creator-docs"
FORK_URL="https://github.com/pernielsentikaer/raycast-extensions.git"
EXTENSION_NAME="roblox-creator-docs"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[greptile-apps]

Greptile Summary

This PR adds Windows platform support to the roblox-creator-docs extension and bumps the version to 1.1.0. The version alignment between package.json and CHANGELOG.md has been resolved since the previous review round.

Two concerns flagged in the prior review round remain unaddressed:

• CHANGELOG.md still uses a hardcoded date (2026-04-20) instead of the required {PR_MERGE_DATE} template variable.
• package-lock.json has a mismatched root version (1.0.1) and shows multiple transitive dependency downgrades (e.g. brace-expansion, minimatch, ajv, flatted), indicating the lock file was regenerated from a stale or incorrect state.

Confidence Score: 4/5

Not safe to merge until the hardcoded CHANGELOG date and stale lock file are corrected.

The package.json version bump was properly addressed from last round, but the two remaining P1-level findings (hardcoded date instead of {PR_MERGE_DATE}, and a stale-state package-lock.json with downgraded transitive deps) still need to be resolved before this can be merged cleanly.

extensions/roblox-creator-docs/package-lock.json and extensions/roblox-creator-docs/CHANGELOG.md

Important Files Changed

Filename	Overview
extensions/roblox-creator-docs/CHANGELOG.md	Adds [1.1.0] Windows Support entry; still uses a hardcoded date (2026-04-20) instead of {PR_MERGE_DATE} placeholder (flagged in prior review round).
extensions/roblox-creator-docs/package.json	Version bumped to 1.1.0 (matching CHANGELOG), contributor added, Windows platform support added — previous version-mismatch concern resolved.
extensions/roblox-creator-docs/package-lock.json	Root-level version is still 1.0.1 (not 1.1.0), and many transitive packages (brace-expansion, minimatch, ajv, picomatch, flatted, etc.) were downgraded; lock file appears generated from a stale state (flagged in prior review round).

_{Reviews (2): Last reviewed commit: "Update package-lock.json" | Re-trigger Greptile}

[greptile-apps]

package-lock.json version downgraded to 1.0.1 and multiple packages rolled back

The root version in package-lock.json was changed from 1.0.2 → 1.0.1, and numerous transitive packages (e.g. brace-expansion, minimatch, ajv, picomatch, flatted) were simultaneously downgraded to older versions. This suggests the lock file was regenerated from a stale state (perhaps from a different branch or an older node_modules). The lock file version must match package.json (1.0.2 or 1.1.0 once bumped), and rolling back transitive deps to older patches undoes previous security/bug fixes. Please regenerate the lock file from a clean install (rm package-lock.json && npm install) against the correct package.json.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/roblox-creator-docs/package-lock.json
Line: 3

Comment:
**`package-lock.json` version downgraded to `1.0.1` and multiple packages rolled back**

The root version in `package-lock.json` was changed from `1.0.2` → `1.0.1`, and numerous transitive packages (e.g. `brace-expansion`, `minimatch`, `ajv`, `picomatch`, `flatted`) were simultaneously downgraded to older versions. This suggests the lock file was regenerated from a stale state (perhaps from a different branch or an older `node_modules`). The lock file version must match `package.json` (`1.0.2` or `1.1.0` once bumped), and rolling back transitive deps to older patches undoes previous security/bug fixes. Please regenerate the lock file from a clean install (`rm package-lock.json && npm install`) against the correct `package.json`.

How can I resolve this? If you propose a fix, please make it concise.

[pernielsentikaer]

This should be ready @0xdhrv 🙂

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/ben_rowlands/roblox-creator-docs

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.