-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add forc-bin
package and upgrade to Forc v0.14.4
#287
Conversation
7c7d2c3
to
70aae11
Compare
24f3276
to
51de976
Compare
forc-bin
package and upgrade to Forc v0.13.0
Noticed some problems after I've asked for reviews and pushed fixes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(async () => { | ||
const pkgPlatform = getPkgPlatform(); | ||
const pkgVersion = await getCurrentVersion(); | ||
const pkgName = `forc-binaries-${pkgPlatform}.tar.gz`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe move all this URLs and repo names to a config file on the root
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, small comment
forc-bin
package and upgrade to Forc v0.13.0forc-bin
package and upgrade to Forc v0.13.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, some of the code from scripts/forc-update.ts
is similar to that inside the forc-bin
package, but I understand why its in a different location.
To clear it up further: How we ideally want to use Forc is discussed on #282. This PR is just some progress on the issue and has no desire to fully resolve it. This PR should be a strict improvement to the project without any regressions, and should also easily be upgradeable to whatever we want to have in the future. My motivation is that even though I can keep this next to my other local scripts and just send an To clear it even further:
|
v0.14.0+ now has predicate support |
cbd029b
to
0618d16
Compare
forc-bin
package and upgrade to Forc v0.13.2forc-bin
package and upgrade to Forc v0.14.4
Updated to 0.14.4 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok, but will defer to the ts experts. Can you file an issue to follow-up with readme documentation on how to bump the version?
This PR is some progress on #282.
feat: add forc-bin package
Adds a new package called
forc-bin
. Packages that need Forc can add this as a dev-depencency and can use it withpnpm forc
. This package can eventually be moved to Sway repo (https://github.com/FuelLabs/pm/issues/19).You can also run
pnpm forc:update
any time, which will:forc-bin
with the latest version on GitHub (if necessary)Forc.lock
spnpm build
to build all Forc projectsfeat: upgrade to Forc v0.13.0
Makes the necessary changes for Forc upgrade.
chore: clean build artifacts
Just a separate commit for visibility. We don't need to commit these anymore.