@unimelb/pattern-lib-vue 14.0.0-beta.2 → 14.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -19,7 +19,7 @@ The contents of this repository have been produced by The University of Melbourn
19
19
 
20
20
  The design system requires:
21
21
 
22
- - [Node](https://nodejs.org/en/) (~6.11.3)
22
+ - [Node](https://nodejs.org/en/) (>=14.17.2)
23
23
  - [Yarn](https://yarnpkg.com/lang/en/docs/install/) (latest version)
24
24
 
25
25
  ```bash
@@ -166,14 +166,12 @@ To deploy to production:
166
166
  1. Bump the `version` number in `package.json` (cf. note below).
167
167
  1. Commit the version change to the `dev` branch.
168
168
  1. Create a pull request to merge the `dev` branch into `master` - e.g. "Deploy v1.0.1".
169
- 1. Wait for the mandatory checks to pass then select "Rebase and merge" (cf. note below).
169
+ 1. Wait for the mandatory checks to pass then select `Create a merge commit`
170
170
 
171
171
  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.
172
172
 
173
173
  > **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.)
174
174
 
175
- > **Note on rebase**: rebasing `dev` onto `master` avoids creating a merge commit that would require merging `master` back into `dev`.
176
-
177
175
  ### Semi-automatic deployment to dev
178
176
 
179
177
  Pre-release builds can be created like this (using the git pre-push hook behind the scenes):
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@unimelb/pattern-lib-vue",
3
3
  "description": "A complete design system for the University of Melbourne.",
4
- "version": "14.0.0-beta.2",
4
+ "version": "14.0.0",
5
5
  "repository": {
6
6
  "type": "git",
7
7
  "url": "https://github.com/unimelb/pattern-lib.git"
@@ -9,7 +9,7 @@
9
9
  "author": "The University of Melbourne",
10
10
  "license": "UNLICENSED",
11
11
  "engines": {
12
- "node": ">=10.0.0",
12
+ "node": ">=14.17.2",
13
13
  "yarn": "*"
14
14
  },
15
15
  "main": ".out/vue.js",
@@ -61,7 +61,8 @@
61
61
  "vue": "2.6.10",
62
62
  "vue-concise-slider": "^3.4.2",
63
63
  "vue-focus-lock": "1.4.0",
64
- "vue-progressive-image": "3.2.0"
64
+ "vue-progressive-image": "3.2.0",
65
+ "xss": "^1.0.14"
65
66
  },
66
67
  "devDependencies": {
67
68
  "@storybook/addon-notes": "^3.4.8",