@borderguru/borderbulk-types
Advanced tools
Comparing version 0.0.0-GO-1527-28-rc-coa-security-issue.2 to 0.0.0-GO-1560-ecargo.1
@@ -55,3 +55,4 @@ export type RegisterDocumentPayload = { | ||
TRANS_GLOBAL_MANIFEST = "TRANS_GLOBAL_MANIFEST", | ||
HRU_MANIFEST_XLSX = "HRU_MANIFEST_XLSX" | ||
HRU_MANIFEST_XLSX = "HRU_MANIFEST_XLSX", | ||
ECARGO_DECLARATION = "ECARGO_DECLARATION", | ||
} |
{ | ||
"name": "@borderguru/borderbulk-types", | ||
"version": "0.0.0-GO-1527-28-rc-coa-security-issue.2", | ||
"version": "0.0.0-GO-1560-ecargo.1", | ||
"description": "TypeScript definitions for BorderGuru SDK", | ||
"main": "index.js", | ||
"scripts": { | ||
"preinstall": "npx npm-force-resolutions" | ||
}, | ||
"scripts": {}, | ||
"repository": { | ||
@@ -19,14 +17,6 @@ "type": "git", | ||
"homepage": "https://bitbucket-prod.doa.otc.hlg.de/projects/GO/repos/borderbulk-types/browse/README.md", | ||
"dependencies": { | ||
"npm-force-resolutions": "0.0.10" | ||
}, | ||
"dependencies": {}, | ||
"devDependencies": { | ||
"@borderguru/borderbulk-scripts": "1.0.1", | ||
"@semantic-release/changelog": "3.0.2", | ||
"@semantic-release/git": "7.0.8", | ||
"semantic-release": "15.13.3" | ||
}, | ||
"resolutions": { | ||
"rc": "1.2.8" | ||
"@borderguru/borderbulk-scripts": "1.0.1" | ||
} | ||
} |
@@ -21,16 +21,12 @@ # BorderBulk Type Definition | ||
* **Merges to master** | ||
* **Publish** | ||
When something is merged to `master` a new release is going to be created using `semantic-release`. Because of this, we are checking PR title to ensure it's using a valid format. | ||
For publish a new version. We will need to create a new version as we do in the other projects. | ||
This repo uses the Squash and Merge convention so make sure the squash commit follows the above commit message convention. | ||
1. Create a branch from master | ||
2. $ npm --no-git-tag-version version $NEW_VERSION | ||
3. Merge the branch into master | ||
If the squash commit message does not match the format mentioned in the contributing section, a NEW release will NOT be created. | ||
And then a new step to publish the version: | ||
A sample squash commit message would be: | ||
`feat: Update BulkTypes` | ||
This would result in a new minor version generated (including updates to the package and package-lock.json) and published to NPM. | ||
N.B: Do not create tags for Borderbulk, npx semantic release handles the part of generating the next version when publishing. | ||
4. $ npm publish |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Install scripts
Supply chain riskInstall scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Found 1 instance in 1 package
0
1
475
0
18306
21
32
- Removednpm-force-resolutions@0.0.10
- Removedbuffer-from@1.1.2(transitive)
- Removedjson-format@1.0.1(transitive)
- Removednpm-force-resolutions@0.0.10(transitive)
- Removedsource-map@0.6.1(transitive)
- Removedsource-map-support@0.5.21(transitive)
- Removedxmlhttprequest@1.8.0(transitive)