@unimelb/pattern-lib-vue - npm Package Compare versions

Comparing version 14.5.4 to 14.6.0

package.json

 {
   "name": "@unimelb/pattern-lib-vue",
   "description": "A complete design system for the University of Melbourne.",
-  "version": "14.5.4",
+  "version": "14.6.0",
   "repository": {
@@ -6,0 +6,0 @@ "type": "git",

README.md

@@ -150,4 +150,3 @@ # Pattern Library
 
-> [!NOTE]
-> **Note on versioning**: the version number follows the [semver](http://semver.org/) convention `MAJOR.MINOR.PATCH`, where: `MAJOR` corresponds to a breaking change (e.g. a change in a component's markup), `MINOR` to a new feature (e.g. a new component, a new feature for an existing component, etc.), and `PATCH` to a bug fix or under-the-hood change (e.g. code clean-up, performance improvement, etc.)
+> [!NOTE] > **Note on versioning**: the version number follows the [semver](http://semver.org/) convention `MAJOR.MINOR.PATCH`, where: `MAJOR` corresponds to a breaking change (e.g. a change in a component's markup), `MINOR` to a new feature (e.g. a new component, a new feature for an existing component, etc.), and `PATCH` to a bug fix or under-the-hood change (e.g. code clean-up, performance improvement, etc.)
 
@@ -176,4 +175,3 @@ 1. Look at all the PRs that were assigned to `next-release` throughout the sprint and identify the highest-level of change (major, minor or patch). Deduce the next release's version number and rename the milestone accordingly.
 
-> [!NOTE]
-> **Note on pre-release versions**: These are legitimate [semver](http://semver.org/) versions. They have the format MAJOR.MINOR.PATCH-beta.NUMBER. **Only** these pre-release versions will be published on `dev`.
+> [!NOTE] > **Note on pre-release versions**: These are legitimate [semver](http://semver.org/) versions. They have the format MAJOR.MINOR.PATCH-beta.NUMBER. **Only** these pre-release versions will be published on `dev`.
 
@@ -221,3 +219,3 @@ 1. Check out a clean `dev` branch
 
-You can run visual snapshot testing using `yarn test:snapshots`. This compares your changes against the latest visual snapshot.  Failed snapshot tests will show a visual diff comparison in `snapshots/__tests__/__image_snapshots__/__diff_output__`.
+You can run visual snapshot testing using `yarn test:snapshots`. This compares your changes against the latest visual snapshot. Failed snapshot tests will show a visual diff comparison in `snapshots/__tests__/__image_snapshots__/__diff_output__`.
 
@@ -224,0 +222,0 @@ If you wish to update the snapshots with your changes run `yarn test:e2e:updatesnapshots`.

No alert changes

Improved metrics

Total package byte prevSize

389556

increased by0.16%

Lines of code

1380

increased by0.07%

Worsened metrics

Number of lines in readme file

235

decreased by-0.84%

No dependency changes