-
Notifications
You must be signed in to change notification settings - Fork 33
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
chore: initial cleanup and scripts for 0.5.0 #149
Conversation
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Co-authored-by: Berend Sliedrecht <[email protected]> Signed-off-by: Timo Glastra <[email protected]>
@@ -13,7 +13,7 @@ jobs: | |||
- uses: actions/checkout@v2 | |||
- uses: actions/setup-node@v3 | |||
with: | |||
node-version: 16.x | |||
node-version: 18.x | |||
cache: yarn | |||
|
|||
# ignore scripts as indy-sdk will try to build and we don't have libindy |
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 can now be deleted in the CI scripts?
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.
Not yet as indy-sdk is still included for 0.3/0.4 snippets
@@ -15,7 +15,7 @@ jobs: | |||
- uses: actions/checkout@v2 | |||
- uses: actions/setup-node@v3 | |||
with: | |||
node-version: 16.x | |||
node-version: 18.x | |||
cache: yarn | |||
|
|||
# ignore scripts as indy-sdk will try to build and we don't have libindy |
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.
Same
@@ -31,7 +31,7 @@ You can do this directly on your machine. | |||
After installing and confirming that Libindy is installed, simply run: |
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.
I guess @credo-ts/rest will be available as soon as we get the 0.5.0 release. In such case Libindy will not be needed, right?
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.
I'm working on updating the REST PR and then releasing a new version. Will update there accordingly
@credo-ts
In a follow up PR i'll add the migration guide