@hafslundnett/hdd-style - npm Package Compare versions

Comparing version 1.0.1 to 1.0.2

package.json

 {
   "name": "@hafslundnett/hdd-style",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "A universal design system used across Hafslund nett",
@@ -5,0 +5,0 @@ "repository": "https://github.com/hafslundnett/hdd-theme",

README.md

@@ -5,2 +5,4 @@ # Hafslund digital designsystem (Hdd)
 [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
+[![Build status](https://hafslundtfs.visualstudio.com/Hafslund%20Nett/_apis/build/status/HDD/hdd-style/hdd-style.build)](https://hafslundtfs.visualstudio.com/Hafslund%20Nett/_build/latest?definitionId=632)
+[![Build status](https://hafslundtfs.visualstudio.com/Hafslund%20Nett/_apis/build/status/HDD/hdd-style/hdd-style.release)](https://hafslundtfs.visualstudio.com/Hafslund%20Nett/_build/latest?definitionId=683)
 
@@ -33,2 +35,3 @@ 'Hafslund digital designsystem' is a design system that can be used across projects while maintaining consistancy. The project follows strict naming guidlines, your can read more about them in the [wiki](https://github.com/hafslundnett/hdd-theme/wiki/Naming-guidelines). Every component should be able to run in a isolated environment without depending on parent classes/elements.
 Please read through our [contributing guidelines](./CONTRIBUTING.md).
+
 ## Versioning
@@ -41,2 +44,15 @@
 
+## Releasing new versions and updating CDN
+
+Azure CDN is used to host fonts and icons from the `cdn/` folder. To update the contents of 
+
+1. Check in the new files under `cdn/`.
+2. If this will be included in a new version of the package: Update the package version in `package.json` and the CDN-url in `variables/fontawesome/_variables.scss`. The three numbers after "hdd-style-release-" should match the package version. If the package version is 1.0.2, then the url bound to `$fa-font-path` should be `https://hafslundnett.azureedge.net/hdd-style-release-1-0-2/icons`.
+3. Check in and get your pull request accepted into develop.
+4. Create a new release-branch and push it to GitHub. The name of the branch should be on the format `release/1.0.2`, given that the package version is 1.0.2. This will start the hdd-style.release build, and upload the contents of `cdn/` to Azure CDN.
+5. Continue to release the new version of hdd-style by packaging and uploading the new version to npm manually.
+6. When everything is ok, merge the release-branch into master, and draft a new release on GitHub.
+
+_**Note:** This process has [room for improvements](https://github.com/hafslundnett/hdd-style/issues/92)._
+
 ## Team
@@ -43,0 +59,0 @@

New alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

59

increased by37.21%

Number of medium supply chain risk alerts

24

decreased by-38.46%

Worsened metrics

Total package byte prevSize

1500253

decreased by-21.81%

Number of package files

197

decreased by-19.59%

Lines of code

2952

decreased by-18.2%

No dependency changes