[pull] main from remotion-dev:main

.claude/commands/release.md

@@ -1,18 +1,21 @@
 - Kill any `turbo` processes that might be running with SIGKILL
 - Run `npm login` (I will manually do 2FA in the browser)
-- Use `op item get "Npmjs" --fields password --reveal` to get the password for NPM.
-- Use `op item get "Npmjs" --otp` to get a one-time password for 2FA.
-- Run `npm token create --name="PublishRemotionXXXXXX" --packages "remotion" --packages "create-video" --packages-and-scopes-permission read-write --bypass-2fa --scopes "@remotion" --otp=<otp>`. Replace XXXXXX with a random string so we have a unique name. Use `op item get "Npmjs" --otp` to get the OTP and pass it via `--otp=`. It will ask for a password, pipe in the password using `<<<`. The NPM token will be printed.
+- Use `op item get "Npmjs" --fields password --reveal --account remotiondev.1password.com` to get the password for NPM.
+- Use `op item get "Npmjs" --otp --account remotiondev.1password.com` to get a one-time password for 2FA.
+- Run `npm token create --name="PublishRemotionXXXXXX" --packages "remotion" --packages "create-video" --packages-and-scopes-permission read-write --bypass-2fa --scopes "@remotion" --otp=<otp>`. Replace XXXXXX with a random string so we have a unique name. Use `op item get "Npmjs" --otp --account remotiondev.1password.com` to get the OTP and pass it via `--otp=`. It will ask for a password, pipe in the password using `echo "$PASSWORD" |`.
 - Run `bun i`
 - Run `bun run build`
-- Check `https://www.npmjs.com/package/remotion` to get the current version number
+- Run `npm view remotion version` to get the current version number
 - Run `bun set-version.ts <version>`, where <version> is the current version plus 1
 - Run `NPM_CONFIG_TOKEN=<token> bun run release` where <token> is the NPM token we just created
 - Generate a changelog in markdown and save it to `/tmp/release-<version>.md`:
   - Run `git log v<previous_version>..v<new_version> --oneline` to get all commits
   - Extract PR numbers from merge commits
   - For each PR, run `gh pr view <number> --json title,author,number,url --jq '"* \(.title) by @\(.author.login) in \(.url)"'`
-  - Categorize PRs into sections: "What's Changed" (features, fixes, improvements), "Internal" (dependency upgrades, tooling, infra), "Docs" (documentation changes), "Templates" (template changes)
-  - Check for new contributors by comparing authors against known contributors
+  - Categorize PRs into sections: "What's Changed", "Templates", "Docs", "Internal"
+  - In "What's Changed", sort items so that entries for the same package are adjacent (no subheadings, just sorted order). Changes to the `remotion` core package should appear first
+  - Strip redundant prefixes from PR titles (e.g. remove "Docs:" from items in the Docs section)
+  - "Templates" is a separate section for any template-\* changes
+  - Check for genuinely new contributors by running `gh api repos/remotion-dev/remotion/contributors --paginate --jq '.[].login'` and comparing against PR authors. Only add a "New Contributors" section for authors not in that list
   - Add `**Full Changelog**: https://github.com/remotion-dev/remotion/compare/v<previous_version>...v<new_version>` at the bottom
   - Use the same format as previous GitHub releases (check with `gh release view v<previous_version>`)