-
Notifications
You must be signed in to change notification settings - Fork 8
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
📝 (releases) deps-dev
coming back as analytics
#744
Comments
@JeromeFitz I think you would like to know this lib vanilla-extract |
🤔 Even weirder, it is only when Thanks for sharing about With Next 13, re-looking at how they prefer styling to take place. May make the move depending on how the next few weeks play out with them. As right now using |
get ready Next.js 13 upgrade guide |
🎉 Exciting times indeed. This is the call-out about |
More than likely going to move back to The original intent of this issue is going to be looked at again soon-ish with the release of 🎉
|
- [x] 📦️ NICE-70 update `dep-up` to patch [skip ci] - [x] ♻️ (esm) NICE-70 add missing `.js` [skip ci] - [x] 🐛 NICE-70 dizzy to animation rewrite [b] Closes #744
Since these are all intertwined, do them all at once and upgrade accordingly. ## Packages ### Upgrade - [x] semantic-release@24 - <https://semantic-release.gitbook.io/semantic-release> - <https://github.com/semantic-release/semantic-release> - [x] @semantic-release/commit-analyzer@13 - <https://github.com/semantic-release/commit-analyzer> - [x] conventional-commits-parser@6 - <https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-parser> - [x] conventional-commits-filter@5 - <https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-commits-filter> ### Remove - ~~@semantic-release/git~~ (Keep) - [x] @semantic-release/github - [x] @semantic-release/npm - [x] @semantic-release/release-notes-generator - [x] semantic-release-commit-filter Still have the issue with #744 but put in some better (commented out for now) debugging to finally figure this out. Not _100%_ sure that every package now doesn't just grip _every_ commit across the monorepo, but we will see. There are worse things I guess. And **changesets** seems to ... you know what I will stop there. 😂
Something goofy going on with the particular selection of:
📦 Add or update compiled files or packages
Always coming back as:
📈 Add or update analytics or track code
This is probably a good point to determine if it is because of the index selection on the emoji find, or if this in general could be greatly reduced in complexity by moving back to a
json
file (that can be dynamically generated) instead of a dynamically created object of information. Instead of trying to finagle a way to add torelease.config.cjs
or other configuration files, may be ideal to just allow for ajson
file swap with some examples. I think it would make things much smaller in general.Could also help with a potential adoption if we can use this is a jumping point RE: #729
The text was updated successfully, but these errors were encountered: