Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Release forc-publish #6891

Open
sdankel opened this issue Feb 5, 2025 · 0 comments
Open

Release forc-publish #6891

sdankel opened this issue Feb 5, 2025 · 0 comments
Assignees
@sdankel
Labels
team:tooling Tooling Team

Comments

@sdankel
Copy link
Member

sdankel commented Feb 5, 2025 •
edited
Loading

Add the plugin to the release CI and add documentation to the mdbook.
@sdankel sdankel added the team:tooling Tooling Team label Feb 5, 2025
@sdankel sdankel self-assigned this Feb 5, 2025
@sdankel sdankel mentioned this issue Feb 5, 2025
Merged
8 tasks
@sdankel sdankel changed the title Release forc.pub Release forc-publish Feb 5, 2025
sdankel added a commit that referenced this issue Feb 11, 2025
@sdankel @esdrubal
@JoshuaBatty @kayagokalp
feat: Add forc-publish plugin (#6890)
eafd99e 
## Description

Closes #6889

Currently it only works when running locally, as the forc.pub server is
not yet live. Allows users to publish a package by running `forc
publish` in the root of the package directory. Workspaces not yet
supported.

It's intentionally not yet added to the release process (will be done in
#6891)

To test it locally, run the
[forc.pub](https://github.com/FuelLabs/forc.pub/) server and web app
locally (see that repo's README for more details).

1. Start DB ./scripts/start_local_db.sh
2. Start server cargo run
3. Start frontend cd app && npm start - opens localhost:3000
4. Get API token from local webapp -> Login with Github -> API Tokens ->
Generate new token
5. Edit `std-lib-core/Forc.toml` and add a version key, i.e. `version =
0.1.0`
6. Run `forc publish` from this branch:
FuelLabs/forc.pub#29 and you'll be prompted to
enter the token.

## Checklist

- [x] I have linked to any relevant issues.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [ ] If my change requires substantial documentation changes, I have
[requested support from the DevRel
team](https://github.com/FuelLabs/devrel-requests/issues/new/choose)
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [ ] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [ ] I have requested a review from the relevant team or maintainers.

---------

Co-authored-by: Marcos Henrich <[email protected]>
Co-authored-by: Joshua Batty <[email protected]>
Co-authored-by: Kaya Gökalp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdankel sdankel

Labels
team:tooling Tooling Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdankel