Skip to content

Conversation

@jakehobbs
Copy link
Contributor

@jakehobbs jakehobbs commented Jan 8, 2026

Pull Request Checklist


PR-Codex overview

This PR introduces a new GitHub Actions workflow named Publish V5 Alpha Packages, which facilitates the publishing of alpha versions of packages. It includes steps for setup, version incrementing, and publishing, with options for dry runs and automated version injection.

Detailed summary

  • Added workflow file .github/workflows/publish-v5-alpha.yml.
  • Defined workflow_dispatch for manual triggering.
  • Configured permissions for GitHub Actions.
  • Implemented steps for checking out code, cleaning disk space, and setting up the environment.
  • Included dry run functionality to preview publishing actions.
  • Added version incrementing and injecting scripts.
  • Committed version changes and published packages to NPM.
  • Managed Lerna configuration files for versioning.
  • Pushed changes and tags to the moldy/v5-base branch.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@vercel
Copy link

vercel bot commented Jan 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
aa-sdk-ui-demo Ready Ready Preview, Comment Jan 9, 2026 6:44pm

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds a GitHub Actions workflow for publishing v5 alpha packages. The workflow enables manual publishing of v5 alpha releases through a workflow dispatch trigger, with built-in dry-run capability for safety.

Key Changes:

  • New GitHub Actions workflow for publishing v5 alpha packages with manual trigger and dry-run mode
  • Updates to the docs-site submodule commit reference

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/publish-v5-alpha.yml Implements automated v5 alpha package publishing with version increment, NPM publish, and git tagging
docs-site Updates submodule reference to latest commit

@github-actions
Copy link

github-actions bot commented Jan 8, 2026

🌿 Documentation Preview

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Jan 9, 2026, 6:39 PM

@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 00:10 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 00:30 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 00:35 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 19:21 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 19:32 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 19:41 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 19:47 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 21:05 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 21:12 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 21:24 Inactive
@github-actions github-actions bot temporarily deployed to docs-preview January 8, 2026 21:30 Inactive
Richard-Dang
Richard-Dang previously approved these changes Jan 9, 2026
fetch-depth: "0"
submodules: "recursive"

- name: Free up disk space
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this required on every run?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good question. i just copied it from the other publishing action.

looks like @blakecduncan added it a couple of months ago b/c the other GHA was running out of disk space: 0c1b48a

CURRENT_VERSION=$(node -p "require('./lerna.json').version")
echo "Current version: $CURRENT_VERSION"
# Calculate next version (increment the number after the last dot)
NEXT_VERSION=$(echo "$CURRENT_VERSION" | awk -F. -v OFS=. '{$NF++; print}')
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we use semvar here instead of manually bumping the version to avoid mismatch between dryrun/actual run versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good idea! updated.

@jakehobbs jakehobbs merged commit eb69d8e into main Jan 9, 2026
14 checks passed
@jakehobbs jakehobbs deleted the jake/v5-alpha-publish branch January 9, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants