Bump Version
code.bump_version
Overview
When you already know which kind of bump you want, we calculate the next Semantic Versioning 2.0.0 string for you — major, minor, patch, prerelease, or release. Lower components and prerelease reset as SemVer requires; release strips prerelease (and build metadata unless you ask to keep it). We do not read commits, edit files, or talk to a registry — do not use this when the bump type must be inferred from commit messages.
SemVer resets and prerelease rules are easy to get wrong by hand. We apply them the same way every time so your tags stay consistent.
Reliability
STRICT and deterministic for identical inputs. Domain errors (not retryable; fix the input — unchanged retry will not succeed): INVALID_SEMVER (currentVersion is not valid SemVer — send a well-formed version); INVALID_BUMP_TYPE (bump missing or not one of major|minor|patch|prerelease|release — pick an allowed value); INVALID_PRERELEASE_IDENTIFIER (prereleaseIdentifier has invalid characters — use alphanumeric and hyphens only); VERSION_COMPONENT_OVERFLOW (a component would exceed representable range — use a smaller currentVersion).
Context footprint
Returns previousVersion, nextVersion, a change summary, and small _meta. A successful call costs 1 execution credit.
When to use it
When you already know the bump kind and need the next version string before tagging.
When the bump must be inferred from commit messages or changelog text.
Scope
Non-goals
- Does not read Git history or commit messages
- Does not modify files
- Does not infer the bump type
- Does not publish releases
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
How we handle your data
What this means
This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.
Squillify guarantees
- Runs inside Squillify
- This skill runs inside Squillify.
- Payloads are not sent to an external service by this skill.
- Squillify does not permanently store submitted payloads.
- Telemetry records metadata only, not submitted content.
- Submitted payloads are not used for training.
- Submitted payloads are not reviewed by humans.
- This skill does not target sensitive data.
- The response may contain submitted or transformed content.
Your responsibility
Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| currentVersion | string | Yes | Current strict Semantic Versioning 2.0.0 value. |
| bump | string | Yes | Explicit bump operation. |
| prereleaseIdentifier | string | No | Prerelease label; omit it to reuse the current label or start rc. |
| zeroMajorPolicy | string | No | 0.x patch policy; omit it for strict_semver. |
| preserveBuildMetadata | boolean | No | Whether build metadata is retained; omit it for false. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| previousVersion | string | Yes | Normalized strict Semantic Versioning 2.0.0 value. |
| nextVersion | string | Yes | Normalized strict Semantic Versioning 2.0.0 value. |
| change | object | Yes | Closed component-change receipt with signed major, minor and patch deltas plus whether prerelease moved. |
| _meta | object | Yes | Closed bump-policy receipt naming the pinned policy version that produced this nextVersion. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"code.bump_version","input":{"currentVersion":"1.2.3","bump":"minor"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("code.bump_version", {"bump":"minor","currentVersion":"1.2.3"});Errors
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
| INVALID_SEMVER | 400 | No | The request payload failed this skill's input validation. |
| INVALID_BUMP_TYPE | 400 | No | The skill does not support the requested variant. |
| INVALID_PRERELEASE_IDENTIFIER | 400 | No | The request payload failed this skill's input validation. |
| VERSION_COMPONENT_OVERFLOW | 429 | No | A size, quota, rate, or time limit was exceeded. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not read Git history or commit messages
- Does not modify files
- Does not infer the bump type
- Does not publish releases
- Deriving the bump from conventional commits
- Writing version files to disk
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "code.bump_version",
"input": {
"bump": "minor",
"currentVersion": "1.2.3"
}
}Examples
Bump minor for a stable release
{
"bump": "minor",
"currentVersion": "1.2.3"
}{
"_meta": {
"policy": "semver-bump-1"
},
"nextVersion": "1.3.0",
"change": {
"prerelease": false,
"minor": 1,
"patch": -3,
"major": 0
},
"previousVersion": "1.2.3"
}Increment an existing prerelease series
{
"bump": "prerelease",
"currentVersion": "1.2.3-beta.2"
}{
"_meta": {
"policy": "semver-bump-1"
},
"nextVersion": "1.2.3-beta.3",
"change": {
"prerelease": true,
"minor": 0,
"patch": 0,
"major": 0
},
"previousVersion": "1.2.3-beta.2"
}Recommended use cases
- Compute the next release version in CI once the bump kind is decided
- Increment a prerelease identifier such as beta.N
- Promote a prerelease to a stable release
Avoid for
- Deriving the bump from conventional commits
- Writing version files to disk
Related skills
Composable with
Safety & privacy
- Runs without calling any external service.
- Your payloads are never stored permanently.
- Telemetry captures metadata only — never your payload contents.
- We never train models on your payloads.
- No human reviews your payloads.