Skip to content

Conversation

@seansica
Copy link
Contributor

@seansica seansica commented Mar 5, 2025

Closes #13

  • Updated build files with the requisite information to publish to npm
  • Updated installation instructions in README and USAGE
  • Tested/verified the artifact can publish to the npm registry
  • Tested/verified users can install the artifact from the npm registry by initializing a new project via npm init and running npm i @mitre-attack/attack-data-model
image

seansica added 3 commits March 5, 2025 16:45
- Add @mitre-attack npm registry info to .npmrc
- Add support for next-major branch to ci.yml
- Uncomment the NPM_TOKEN environment variable that toggles the "@semantic-release/npm" plugins ability to publish

This is not a breaking change, but it may temporarily break the CI pipeline
- Remove registry key (already specified by .npmrc)
- Add access key (set to public)
@seansica seansica self-assigned this Mar 5, 2025
@seansica seansica linked an issue Mar 5, 2025 that may be closed by this pull request
@seansica seansica merged commit 5648da4 into main Mar 5, 2025
8 checks passed
@seansica seansica deleted the next branch March 5, 2025 22:21
@github-actions
Copy link

github-actions bot commented Apr 2, 2025

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

🎉 This PR is included in version 1.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

🎉 This PR is included in version 1.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish to NPM?

2 participants