new canary workflow & stylelint-config#111
Conversation
|
/canary-publish |
…tection and dependency management
dfda66e to
05bdf8e
Compare
|
@yujeong-jeon , Could you help me figure out what’s causing the issue? I just pushed two new commits. 🤔 NaverPayDev/changeset-actions@c46d567 |
|
Looks like there are two issues here—one related to the default export, and the other has something to do with the GitHub path. 🤔 @yujeong-jeon |
✅ Changeset detectedLatest commit: 098e2aa
If no version change is needed, please add The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
|
|
Issue resolved. The problem was caused by a missing |
|
thanks @yujeong-jeon you just saved my life |
|
/canary-publish |
|
canary-publish action can be run on |
I don’t think that’s quite right…😂 |
Gooooooooo |
This pull request introduces several updates, including the addition of a new GitHub Actions workflow for Canary releases, renaming and updating the release workflow, and dependency updates across multiple files. Below is a breakdown of the key changes:
GitHub Actions Workflows
.github/workflows/canary.yml) triggered by specific issue comments (canary-publishor/canary-publish) to automate Canary releases. It includes steps for checking out the PR branch, setting up Node.js and pnpm, and publishing the Canary version using a specified script..github/workflows/changeset-publish.ymlto.github/workflows/release.ymland updated its configuration. Changes include renaming the job frompublishtorelease, improving step names for clarity, and updating thechangeset-actions/publishconfiguration with corrected parameters and formatting. [1] [2]Dependency Updates
package.jsonUpdate: Updated thevitedependency from version^6.2.0to^6.3.5.packages/stylelint-config/package.jsonUpdates:postcssandpostcss-scsstopeerDependencieswith updated versions.stylelint,stylelint-order, andstylelint-scssto newer versions underdependencies.