@unimelb/pattern-lib-vue 14.5.4 → 14.6.0

package/README.md

@@ -147,8 +147,7 @@ For your own sanity, make sure to install your code editor's ESLint and stylelin
 
 **At the end of the release sprint:**
 
-> [!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.)
 
 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.
 1. Create a new release notes draft based on the following template: `.github/RELEASE_NOTES_TEMPLATE.md`.
@@ -172,8 +171,7 @@ For your own sanity, make sure to install your code editor's ESLint and stylelin
 
 Pre-release builds can be created like this (using the git pre-push hook behind the scenes):
 
-> [!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`.
 
 1. Check out a clean `dev` branch
 1. in bash `git push` - this will increment the pre-release version number and make a commit to your local repository
@@ -216,7 +214,7 @@ Recommended mobile devices for testing:
 
 ### Visual snapshot testing
 
-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__`.
 
 If you wish to update the snapshots with your changes run `yarn test:e2e:updatesnapshots`.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@unimelb/pattern-lib-vue",
   "description": "A complete design system for the University of Melbourne.",
-  "version": "14.5.4",
+  "version": "14.6.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/unimelb/pattern-lib.git"