-
Notifications
You must be signed in to change notification settings - Fork 281
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(ci): update deprecated GitHub API #2368
Conversation
ad1813f
to
ae072be
Compare
e9f13d8
to
23ca171
Compare
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.
@ryjones Please pin the jobs to exact versions. For example for actions/setup-node the latest is v3.6.0
(same applies to all the other ones)
Telling the typescript compiler to skip the library code check so that auto-updating dependencies don't break the test fixture chain code compilation. The root cause and the fix are equivalent as they were for: https://github.com/hyperledger/cacti/issues/2322 https://github.com/hyperledger/cacti/pull/2323 Commit SHA: dfb7278 Fixes #2341 Also sneaking in a .gitignore change with this: there is a VSCode extension that stores local editing history of files in a .history/ sub-folder and that needs to be ignored in git otherwise it just keeps popping up in the git index which is annoying sometimes. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
6ab7f72
to
d56d63a
Compare
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.
@ryjones LGTM thank you
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
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
…ata sharing Signed-off-by: Sandeep Nishad <sandeep.nishad1@ibm.com>
Signed-off-by: Ry Jones <ry@linux.com>
I did |
@sandeepnRES My best guess is that you did a pull with merge by accident locally at some point before you did that With that said, the 2 other commits were successfully disappeared when Ry hit 'rebase and merge' (I assume) so luckily we did not mess up and duplicate the commits. |
Use current version of GitHub action