publish mashlib from release.yml orchestrator
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
the actual SolidOS as a multi repos makes npm publish lengthy and boring specialy for publishing test versions to npm.
An orchestrator helps to do it quickly.
A work in progress is now available release.yml
It is launched manually from the menu button Actions.
It has been tested :
- to publish at
npm <repos> --tag testfrom a selected branch - more tests will be done quickly to validate
npm <repos> --tag latestfrommain
The published stack is defined from a config file.
Default full stack is release.config.json.
Other files can be created to define what should be published. Example with release.profile-pane.config.json
Notes
Due to npm limitation to only allow one github repo for OIDC trusted.
All SolidOS stack repos on npm MUST allow 2FA AND tokens for the orchestrator
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review .github/workflows/release.yml and the stack definitions in release.config.json and release.profile-pane.config.json. Start by running the manually triggered workflow from the Actions menu and checking its existing test-version publishing behavior. Done means the orchestrator can publish mashlib as part of the selected stack with the documented npm tags and trusted-publishing requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100