You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going to create a new PR for bumping a new version (v1.15.2) so the process can be repeated without deleting the previously generated tag (v1.15.1).
Tip
Also, may I suggest to name the release posts using the release number "e.g.: v1.15.1"?
Having long names like "Maintenance Release" is unusual IMHO. WDYT?
The text was updated successfully, but these errors were encountered:
@elycruz I see you created a new release on GitHub but the release has not been published to npm.
As you can in the below link, the related GitHub Actions run is failed:
https://github.com/elycruz/rollup-plugin-sass/actions/runs/12709589453/job/35428910013
The reason is that you haven't bumped the version number in
package.json
/package-lock.json
:rollup-plugin-sass/package.json
Line 3 in 6712bd2
rollup-plugin-sass/package-lock.json
Line 3 in 6712bd2
I'm going to create a new PR for bumping a new version (v1.15.2) so the process can be repeated without deleting the previously generated tag (v1.15.1).
Tip
Also, may I suggest to name the release posts using the release number "e.g.: v1.15.1"?
Having long names like "Maintenance Release" is unusual IMHO. WDYT?
The text was updated successfully, but these errors were encountered: