Skip to content

Conversation

@thecrypticace
Copy link
Contributor

No description provided.

@thecrypticace thecrypticace requested a review from a team as a code owner September 30, 2025 20:45
RobinMalfait and others added 7 commits October 1, 2025 11:24
The `version` could be _ahead_ when we are preparing a new release. The
version in package.json will point to e.g. 4.1.4 while the latest
version (on npm) is 4.1.3

We _know_ that in these tests we have `v3` as the current package, not
`v3.0.0` so the regex should not change these values.
While looking at the message in CI I noticed that we used backticks
around node_modules but not around the package.json

We also show `/ lockfile` but I don't think that's entirely correct, so
dropped it.

With this change, we see a better message:

```diff
- "tailwindcss": "^3" (expected version in `package.json`)
+ "tailwindcss": "4.0.0" (installed version in `node_modules`)
```
Because we're not actually releasing this yet
- `in React` is not really relevant
- Added backticks around `className` to be consistent
- Prefixed some entries with `Upgrade:`
@thecrypticace thecrypticace merged commit b67cbcf into main Oct 1, 2025
12 of 13 checks passed
@thecrypticace thecrypticace deleted the release/4.1.14 branch October 1, 2025 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants