Skip to content

Refactor TinaCloud release automation #6385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
kulesy wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Refactor TinaCloud release automation #6385

kulesy wants to merge 6 commits into from
+23 −90

Conversation

@kulesy
Copy link
Contributor

@kulesy kulesy commented Jan 30, 2026 •
edited
Loading

Summary

Refactors the TinaCloud release automation to be more extensible. Instead of tinacms computing version bumps and triggering tinacloud for specific packages, tinacms now sends all published packages and tinacloud handles the filtering.

Changes

tinacms

  • publish.yml: Now sends all published packages to tinacloud via tinacms-release dispatch event
  • Removed label-based triggering logic
  • Deleted add-tinacloud-release-label.yml workflow

tinacloud

  • update-tinacms-graphql.yml: Renamed to "Update TinaCMS Dependencies"
  • Receives all packages and filters using a packageMappings config
  • Computes bump type by comparing incoming version to current version in package.json
  • Easy to extend - just add entries to packageMappings:
const packageMappings = {
  '@tinacms/graphql': {
    file: 'js/content-api/package.json',
    depType: 'dependencies',
    addAlias: true
  }
  // Add more packages here as needed
};

Flow

  1. tinacms publishes packages via changesets
  2. Notifies tinacloud with all published packages
  3. tinacloud filters for packages it cares about
  4. If relevant updates found, creates a PR

Test Plan

  • Manual workflow dispatch test in tinacloud
  • Verify PR creation with correct version updates

claude added 3 commits January 30, 2026 00:44
@claude
feat: add workflow to label PRs requiring TinaCloud release
5b39cf5 
This adds a new workflow that automatically adds a "requires-tinacloud-release"
label to Version Packages PRs when @tinacms/graphql has a minor or major bump.

This helps identify before merge that a TinaCloud release will be needed.

https://claude.ai/code/session_01DTjHgRcXFjSP7dztVKGZUF
@claude
refactor: use label check instead of version bump detection in publis…
74d896b 
…h.yml

Instead of re-computing whether @tinacms/graphql has a minor/major bump,
the publish workflow now checks if the merged "Version Packages" PR has
the "requires-tinacloud-release" label (added by the new label workflow).

This simplifies the logic and ensures consistency between the label
(visible before merge) and the tinacloud trigger (after publish).

https://claude.ai/code/session_01DTjHgRcXFjSP7dztVKGZUF
@claude
refactor: use direct commit-to-PR lookup in publish.yml
6f294ab 
Replace pulls.list with listPullRequestsAssociatedWithCommit for finding
the Version Packages PR. This is more reliable as it directly queries by
merge commit SHA instead of hoping the PR is in the 10 most recently
updated closed PRs.

https://claude.ai/code/session_01DTjHgRcXFjSP7dztVKGZUF
@kulesy kulesy requested a review from a team as a code owner January 30, 2026 01:22
@changeset-bot
Copy link

changeset-bot bot commented Jan 30, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: d8948cd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Jan 30, 2026 •
edited
Loading

Playwright E2E Test Results

passed  7 passed
skipped  2 skipped

Details

stats  9 tests across 6 suites
duration  34.1 seconds
commit  d8948cd

Skipped tests

chromium › retain-input-value-from-localstorage.spec.ts › Local storage retain edit test
chromium › rich-text-editor/newline-parsing.spec.ts › should be able to parse newline from markdown

@kulesy kulesy changed the title Refactor TinaCloud release automation to use PR labels Refactor TinaCloud release automation Jan 30, 2026
@kulesy
refactor: simplify tinacloud release automation
a8a8076 
- Remove label-based triggering (delete add-tinacloud-release-label.yml)
- Send all published packages to tinacloud on every release
- Let tinacloud filter for packages it cares about
18-th
18-th reviewed Feb 2, 2026
View reviewed changes
18-th
18-th approved these changes Feb 2, 2026
View reviewed changes
Copy link
Contributor

@18-th 18-th left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@18-th 18-th 18-th approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kulesy @18-th @claude