Skip to content

chore(release): version packages on main branch #2658

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

Merged
merged 1 commit into from
Apr 8, 2025

Conversation

janus-idp[bot]
Copy link
Contributor

@janus-idp janus-idp bot commented Apr 4, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@janus-idp/[email protected]

Patch Changes

  • a3e8716: Prepare for better compatibility with the upstream dynamic plugins support, by generating the config schema for backend plugins in both dist/configSchema.json (for backward compatibility with RHDH) and dist/.config-schema.json for consistency and compatibility with upstream.
  • 2559fd7: This change fixes package-dynamic-plugin to transform any organization identifier into a flat file path when packaging dynamic plugins.

@davidfestal
Copy link
Member

/lgtm

@janus-idp janus-idp bot force-pushed the changeset-release/main branch from dae36bc to 9ea306d Compare April 7, 2025 10:26
@openshift-ci openshift-ci bot removed the lgtm label Apr 7, 2025
Copy link

sonarqubecloud bot commented Apr 7, 2025

@openshift-ci openshift-ci bot added the lgtm label Apr 8, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 95af580 into main Apr 8, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the changeset-release/main branch April 8, 2025 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants