# google/skills Release Cycle: How Continuous Deployment Works

> Discover the google/skills release cycle. Learn how continuous deployment merges changes directly to main after CI checks, ensuring rapid updates for the google/skills project.

- Repository: [Google/skills](https://github.com/google/skills)
- Tags: how-to-guide
- Published: 2026-08-16

---

**The google/skills repository uses a rolling (continuous) release model where changes merge to `main` immediately after passing CI checks, with optional tagged releases for major milestones.**

This open-source skill repository distributes Google Cloud learning materials through an **ad-hoc release strategy** rather than fixed calendar dates. Understanding this cadence helps contributors and users know when to expect updates and how to pin specific versions.

## Understanding the google/skills Release Model

The repository prioritizes **speed of delivery** over scheduled releases. Every pull request triggers automated validation through GitHub Actions workflows in `.github/workflows/`, and successful merges land on `main` instantly.

Users always receive the freshest skills via:

```bash
npx skills add google/skills

```

This command pulls directly from the current `main` state, making the concept of "latest release" effectively continuous.

## The Four-Stage Release Workflow

| Stage | Action | Location in Repository |
|-------|--------|------------------------|
| **Continuous Integration** | Automated build, test, and validation on every PR | `.github/workflows/*` |
| **Merge to `main`** | Instant availability after CI success | `main` branch |
| **Tag & Release** | Optional version tag for milestone grouping | `git tag` + GitHub Releases |
| **User Installation** | Pull latest or specific tagged version | [`README.md`](https://github.com/google/skills/blob/main/README.md) documentation |

## When Tagged Releases Occur

Tagged releases are **not calendar-driven**. According to the repository's workflow, maintainers create a GitHub tag (e.g., `v1.2.0`) when:

- A **major feature set** reaches completion
- A **new Google Cloud product** receives comprehensive skill coverage
- **Breaking changes** require user attention

These releases appear at `https://github.com/google/skills/releases` with corresponding release notes, but no committed schedule exists.

## How to Install Specific Versions

While `npx skills add google/skills` fetches the rolling latest, you can pin to tagged releases:

```bash

# View all available tags

git ls-remote --tags https://github.com/google/skills.git

# Install a specific release

npx skills add google/skills@v1.3.0

```

Individual skills reside in `skills/*` directories with their own [`SKILL.md`](https://github.com/google/skills/blob/main/SKILL.md) definitions—for example, [`skills/cloud/bigquery-basics/SKILL.md`](https://github.com/google/skills/blob/main/skills/cloud/bigquery-basics/SKILL.md)—all updated continuously without separate versioning.

## Key Files That Define the Release Process

- **[`README.md`](https://github.com/google/skills/blob/main/README.md)** — Documents the rolling release installation pattern
- **[`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md)** — Explains continuous merge expectations for contributors
- **`.github/workflows/*`** — Enforces quality gates enabling auto-merge to `main`

## Summary

- The **google/skills release cycle** is **continuous**, not calendar-based
- Changes reach users **immediately** after CI passes via the `main` branch
- **Tagged releases are optional** and triggered by maintainers for significant milestones
- Users install via `npx skills add google/skills` for latest, or append `@version` to pin

## Frequently Asked Questions

### Does google/skills follow semantic versioning on a schedule?

No. The repository uses semver-style tags (e.g., `v1.2.0`) but applies them **ad-hoc** when maintainers judge a feature set worthy of formal release, not on fixed intervals like monthly or quarterly cycles.

### How do I know what version I'm running?

The `npx skills add` command fetches from `main` by default with no explicit version. To check available tagged releases, run `git ls-remote --tags https://github.com/google/skills.git` or visit the repository's GitHub Releases page.

### Can I contribute to a specific upcoming release?

Contributions merge continuously to `main` once CI checks in `.github/workflows/*` pass. There are no release branches or feature freezes—the [`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md) guidelines emphasize this rolling integration approach.

### Is the continuous release model documented officially?

Yes. The [`README.md`](https://github.com/google/skills/blob/main/README.md) describes installation via `npx skills add google/skills` as the primary method, reflecting the rolling release design where the latest `main` commit is always considered production-ready.