Skip to content
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.

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

chore: merge 22.x into 23.x for release config #3346

Closed
wants to merge 3 commits into from

Conversation

brian-smith-tcril
Copy link
Contributor

Description

Include a description of your changes here, along with a link to any relevant Jira tickets and/or Github issues.

Deploy Preview

Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).

Merge Checklist

  • If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
  • Does your change adhere to the documented style conventions?
  • Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
  • Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
  • Were your changes tested in the example app?
  • Is there adequate test coverage for your changes?
  • Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please request an a11y review for the PR in the #wg-paragon Open edX Slack channel.

Post-merge Checklist

  • Verify your changes were released to NPM at the expected version.
  • If you'd like, share your contribution in #show-and-tell.
  • 🎉 🙌 Celebrate! Thanks for your contribution.

* build: update `.releaserc` to publish from appropriate branches

* chore: dry run new semantic release config
Semantic release requires at least 1 branch be configured as "release" (see https://github.com/semantic-release/semantic-release/blob/master/docs/usage/workflow-configuration.md#branches-properties)

Before this change we had 2 "maintenance" branches and 1 "pre-release" branch, but no "release" branch. This led to an error https://github.com/openedx/paragon/actions/runs/12286316911/job/34286199225
Copy link

netlify bot commented Dec 11, 2024

Deploy Preview for paragon-openedx-v22 ready!

Name Link
🔨 Latest commit c6e1eb4
🔍 Latest deploy log https://app.netlify.com/sites/paragon-openedx-v22/deploys/675a22c5202a5d000848ada5
😎 Deploy Preview https://deploy-preview-3346--paragon-openedx-v22.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Dec 11, 2024

Deploy Preview for paragon-openedx-v23 ready!

Name Link
🔨 Latest commit c6e1eb4
🔍 Latest deploy log https://app.netlify.com/sites/paragon-openedx-v23/deploys/675a22c50a130d0008cdf421
😎 Deploy Preview https://deploy-preview-3346--paragon-openedx-v23.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@brian-smith-tcril
Copy link
Contributor Author

closing to handle in a new branch to resolve conflicts

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.

1 participant