Skip to main content

Squillify development is paused indefinitely. Read why, and discover what this experiment achieved. Read the story

MicroSkills Reference

Bump Version

code.bump_version

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0
No network

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

Note
Computes the next SemVer 2.0.0 string from an explicit bump you choose.

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

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

generationparsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input1 KB

How we handle your data

Sensitive output possible
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.

Read the Microskill Data Handling Policy

Input schema

FieldTypeRequiredDescription
currentVersionstringYesCurrent strict Semantic Versioning 2.0.0 value.
bumpstringYesExplicit bump operation.
prereleaseIdentifierstringNoPrerelease label; omit it to reuse the current label or start rc.
zeroMajorPolicystringNo0.x patch policy; omit it for strict_semver.
preserveBuildMetadatabooleanNoWhether build metadata is retained; omit it for false.

Output schema

FieldTypeRequiredDescription
previousVersionstringYesNormalized strict Semantic Versioning 2.0.0 value.
nextVersionstringYesNormalized strict Semantic Versioning 2.0.0 value.
changeobjectYesClosed component-change receipt with signed major, minor and patch deltas plus whether prerelease moved.
_metaobjectYesClosed bump-policy receipt naming the pinned policy version that produced this nextVersion.

API contract

POST /v1/execute
curl
curl -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"}}'
Integrations
TypeScript SDK
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

CodeHTTPRetryableDescription
VALIDATION_ERROR400NoThe request payload failed schema validation.
UNAUTHORIZED401NoMissing or invalid API key.
SKILL_NOT_ACCESSIBLE403NoThe API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN403NoThis skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE503YesPlan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND404NoThe requested skill or version does not exist.
TENANT_RATE_LIMITED429YesRequest rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED429YesPlan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT504YesExecution exceeded the allowed time budget.
INVALID_SEMVER400NoThe request payload failed this skill's input validation.
INVALID_BUMP_TYPE400NoThe skill does not support the requested variant.
INVALID_PRERELEASE_IDENTIFIER400NoThe request payload failed this skill's input validation.
VERSION_COMPONENT_OVERFLOW429NoA size, quota, rate, or time limit was exceeded.

Other limits

LimitValue
Recommended inline bytes32 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)

Request bodyjson
{
  "skillKey": "code.bump_version",
  "input": {
    "bump": "minor",
    "currentVersion": "1.2.3"
  }
}

Examples

Bump minor for a stable release

Inputjson
{
  "bump": "minor",
  "currentVersion": "1.2.3"
}
Expected outputjson
{
  "_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

Inputjson
{
  "bump": "prerelease",
  "currentVersion": "1.2.3-beta.2"
}
Expected outputjson
{
  "_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"
}
  • 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

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.

Tags

codesemvergeneration