-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup this repo to deploy to NPM #2
Comments
Lukas has renamed the package to manifesto3d in the package.json file (already committed) to support the deployment in npm without interfering with the existing manifesto.js npm package. I think with that change we can also change the version to a simpler npm semantic version. The version of the package is now "4.3.0-draft3dapi.0.5.0" ; the 4.3.0 refers to the latest manifesto.js version. I would propose setting the manifesto3d package.json version to 0.5.0; I leave it to Lukas to make that change if he agrees. I will also recompile the modules with the new package name, commit them to a branch of iiif-commons/manifesto3d that I have created named kshell-dev. I will create a pull request to move those new compiled modules into master, and at that time we'll make sure we're all rowing in the same direction. |
Wasn't able to continue work here yesterday, so I try to set up a working NPM publishing pipeline today. |
I think everything should be in place now. The only thing I can't do is to set the NPM Token secret in the settings of the Repo. @glenrobson I think you can access the settings to set the secret. After setting them, a release with a new Tag should do the trick, I suppose. |
Notes from todays meeting:
|
Deployment to NPM was implemented at IIIF-Commons call on July 17 2024 |
Change the following:
https://github.com/IIIF-Commons/manifesto-3d/blob/master/.github/workflows/release.yml
To deploy to NPM but not to overwrite the existing latest version at:
https://www.npmjs.com/package/manifesto.js
@edsilv to invite @luguenth to the NPM iiif-commons repo.
The text was updated successfully, but these errors were encountered: