Skip to content

Update all npm upstream packages #16

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
Merged
oalders merged 1 commit into from
Oct 31, 2022
Merged

Update all npm upstream packages #16

oalders merged 1 commit into from
Oct 31, 2022

Conversation

@atoomic
Copy link
Member

@atoomic atoomic commented Oct 31, 2022

No description provided.

@atoomic atoomic requested a review from oalders October 31, 2022 16:06
@atoomic atoomic mentioned this pull request Oct 31, 2022
Closed
@atoomic
Copy link
Member Author

atoomic commented Oct 31, 2022

In addition to the CI tests, I tried to use it via
atoomic/Path-Tiny@4a75664

Workflow ran, the core
https://github.com/atoomic/Path-Tiny/actions/runs/3362858711/jobs/5575166274

still noticed the warning as set-output is still there

node_modules/@actions/core/lib/core.js:167:    command_1.issueCommand('set-output', { name }, utils_1.toCommandValue(value));

@oalders oalders merged commit 1fe3cda into master Oct 31, 2022
@oalders oalders deleted the npm-full-update branch October 31, 2022 16:38
@atoomic
Copy link
Member Author

atoomic commented Oct 31, 2022

Tagged it as v1.6 so we could start gathering some experience with it before promoting it to stable in short future
Ideally would need a fix from upstream for #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@oalders oalders oalders approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@atoomic @oalders