Repository navigation
chore: stop publishing and Dependabot, point to pie-elements-ng (PIE-883) - #3142
Merged
Merged
Conversation
Publishing moves to pie-framework/pie-elements-ng, which takes over the npm trusted-publisher records for these package names. npm allows one trusted publisher per package, so once this repo's records are revoked a publish from here fails with ENEEDAUTH. Removing the publish jobs (build-next, version/publish or build-release, publish-missing) means a merge here cannot attempt one, and keeps a stray merge from publishing in the meantime. The test job is unchanged.
This repo is no longer maintained: development and npm publishing moved to pie-framework/pie-elements-ng. Remove the Dependabot version-update config so it stops opening PRs here, and add a notice to the README.
CarlaCostea
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retires this repo as an active project. Development and npm publishing for these package names move to pie-elements-ng, which takes over their npm trusted-publisher records (PIE-883).
ci.ymlkeeps only thetestjob. The publish jobs are removed, along with theworkflow_dispatchinput that onlypublish-missingused..github/dependabot.ymlis removed, so Dependabot stops opening version-update PRs here.README.mdopens with a notice pointing to pie-elements-ng.Why now: npm allows one trusted publisher per package, and the records for these names still point at this repo's
ci.yml. They're about to be revoked and re-claimed for pie-elements-ng, after which any publish from here fails withENEEDAUTH. Until then, a develop merge that touches a package would still publish anextcanary.Merging publishes nothing: a push runs the
ci.ymlin the pushed commit, so the merge itself runs the new test-only workflow.Why there's a PR for each branch: develop and master both publish and have diverged, so each gets its own PR, and a develop → master promotion isn't needed. Merge both PRs.
Not affected: the
13.2.2-beta.*builds, which are published by hand, not through CI.Matching PR into
master: #3143