Skip to content

chore(repo): Backport canary package release into v4#2066

Merged
anagstef merged 1 commit intorelease/v4from
backport-release/v4-2015
Nov 7, 2023
Merged

chore(repo): Backport canary package release into v4#2066
anagstef merged 1 commit intorelease/v4from
backport-release/v4-2015

Conversation

@anagstef
Copy link
Copy Markdown
Member

@anagstef anagstef commented Nov 7, 2023

Description

This is a backport PR from #2015

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Packages affected

  • @clerk/backend
  • @clerk/chrome-extension
  • @clerk/clerk-js
  • @clerk/clerk-expo
  • @clerk/fastify
  • gatsby-plugin-clerk
  • @clerk/localizations
  • @clerk/nextjs
  • @clerk/clerk-react
  • @clerk/remix
  • @clerk/clerk-sdk-node
  • @clerk/shared
  • @clerk/themes
  • @clerk/types
  • build/tooling/chore

@anagstef anagstef self-assigned this Nov 7, 2023
@anagstef anagstef requested a review from a team as a code owner November 7, 2023 10:03
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Nov 7, 2023

🦋 Changeset detected

Latest commit: c4c7346

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages
Name Type
@clerk/clerk-js Patch
@clerk/shared Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch
@clerk/backend Patch
@clerk/fastify Patch
@clerk/nextjs Patch
@clerk/clerk-react Patch
@clerk/remix Patch
@clerk/clerk-sdk-node Patch
gatsby-plugin-clerk Patch

Not sure what this means? Click here to learn what changesets are.

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

Comment thread packages/clerk-js/scripts/purge-cache.mjs
push:
branches:
- main
- release/v4
Copy link
Copy Markdown
Contributor

@dimkl dimkl Nov 7, 2023

Choose a reason for hiding this comment

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

🤔 We probably need to add both branched in main and add a condition for this action to block it in pre-release tags. Let's make this change in another PR, to have consistent and identical workflows.

@anagstef anagstef force-pushed the backport-release/v4-2015 branch from 5a75a45 to c4c7346 Compare November 7, 2023 10:37
@anagstef anagstef enabled auto-merge November 7, 2023 10:43
@anagstef anagstef added this pull request to the merge queue Nov 7, 2023
Merged via the queue into release/v4 with commit 4c34290 Nov 7, 2023
@anagstef anagstef deleted the backport-release/v4-2015 branch November 7, 2023 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants