@unimelb/pattern-lib-vue 14.2.4 → 14.3.1

package/README.md

@@ -166,7 +166,7 @@ To deploy to production:
 1. Create a pull request to merge the `dev` branch into `master` - e.g. "Deploy v1.0.1".
 1. Wait for the mandatory checks to pass then select `Create a merge commit`
 
-Semaphore then automatically builds the library and syncs the output files to S3. If the version you're deploying had been previously deployed, you'll need to invalidate the files on the CDN (AWS Cloudfront) or wait a day or so for this to happen automatically. Once the library is deployed, follow the release process below.
+Github Actions then automatically builds the library and syncs the output files to S3. If the version you're deploying had been previously deployed, you'll need to invalidate the files on the CDN (AWS Cloudfront) or wait a day or so for this to happen automatically. Once the library is deployed, follow the release process below.
 
 > **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.)
 
@@ -180,7 +180,7 @@ Pre-release builds can be created like this (using the git pre-push hook behind
 1. in bash `git push` again
   - You will be prompted that this will trigger a build. Answer 'y'
   - This will push (only) your version number change commit to the remote `dev` repo
-1. After the normal checks a build with the new version will be triggered by Semaphore
+1. After the normal checks a build with the new version will be triggered by Github Actions
 
 > **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`.
 
@@ -188,11 +188,11 @@ Pre-release builds can be created like this (using the git pre-push hook behind
 
 ### How could you test before going live?
 
-> The `dev` branch is set up into `Semaphore CI` to deploy into the AWS S3 Bucket in a folder called `latest` where the `CMS` team can appoint to `latest` and test it out before go to `production`.
+> Code changes to the remote `dev` branch triggers a `Github Actions` deploy into the AWS S3 Bucket in a folder called `latest` where the `CMS` team can appoint to `latest` and test it out before go to `production`.
 
 > Each `pull request` that is opened, also is automatically generated a comment with a preview link to test it.
 
-> **Note**: Always check the `Semaphore CI` check into your `pull request` and make sure is building properly, before merge into `dev`.
+> **Note**: Always check `Github Actions` in your `pull request` checks to insure it is building properly, before merge into `dev`.
 
 Supported browsers:
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@unimelb/pattern-lib-vue",
   "description": "A complete design system for the University of Melbourne.",
-  "version": "14.2.4",
+  "version": "14.3.1",
   "repository": {
     "type": "git",
     "url": "https://github.com/unimelb/pattern-lib.git"
@@ -131,9 +131,9 @@
     "stylelint-config-property-sort-order-smacss": "^5.0.0",
     "stylelint-config-standard": "^19.0.0",
     "stylelint-order": "^3.1.1",
-    "svg-fill-loader": "^0.0.8",
     "svg-sprite-loader": "^4.3.0",
     "svg-url-loader": "^2.3.3",
+    "svgo-loader": "^2.1.0",
     "vue-axe": "^1.0.7",
     "vue-html-loader": "^1.2.4",
     "vue-jest": "^2.6.0",