Cf Temp Mail Version Upgrade
Developmentcf-temp-mail-version-upgradeCf Temp Mail Version Upgrade is an Agent Skill for development published in the dreamhunter2333/cloudflare_temp_email repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Upgrade the project version number. Use when the user asks to bump the version, upgrade the version, or prepare a new release version. Supports major, minor, and patch upgrades.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/dreamhunter2333/cloudflare_temp_email/blob/HEAD/.claude/skills/cf-temp-mail-version-upgrade/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cf-temp-mail-version-upgrade, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Version Upgrade
Upgrade the version number of the cloudflare_temp_email project.
Files to modify
frontend/package.json—versionfieldworker/package.json—versionfieldworker/src/constants.ts—VERSIONconstant (format:VERSION: 'v' + '1.4.0')pages/package.json—versionfieldvitepress-docs/package.json—versionfieldCHANGELOG.md— add new version placeholderCHANGELOG_EN.md— add new version placeholder (English)
Upgrade workflow
- Read
frontend/package.jsonto get the current version. - Compute the new version based on the upgrade type:
- major: 1.3.0 → 2.0.0
- minor: 1.3.0 → 1.4.0
- patch: 1.3.0 → 1.3.1
- Update the
versionfield in everypackage.jsonlisted above. - Update the
VERSIONconstant inworker/src/constants.ts. - Insert a new version placeholder at the top of
CHANGELOG.md. - Insert a new version placeholder at the top of
CHANGELOG_EN.md. - Rename the previous version heading in both changelogs from
## v{OLD_VERSION}(main)to## v{OLD_VERSION}so only the new active development version keeps(main).
CHANGELOG format
In CHANGELOG.md, insert before the existing ## v{OLD_VERSION}(main) line (i.e. right after the closing </p> of the language-switch link):
## v{VERSION}(main)
### Features
### Bug Fixes
### Improvements
After inserting the new placeholder, update the old heading:
-## v{OLD_VERSION}(main)
+## v{OLD_VERSION}
CHANGELOG_EN.md uses the same format and must receive the same old-heading update.
Commit message format
feat: upgrade version to v{VERSION}
- Update version number to {VERSION} in all package.json files
- Add v{VERSION} placeholder in CHANGELOG.md
- Move (main) marker from v{OLD_VERSION} to v{VERSION}