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.

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

Core-Consumer interactions improvements #30

Closed
wants to merge 10 commits into from

Conversation

dhilt
Copy link
Owner

@dhilt dhilt commented Oct 5, 2021

For issue #29.

List of changes:

  • export WorkflowParams type
  • use package-lock.json v2 (reproducible build)
  • ...

darcyparker and others added 7 commits October 4, 2021 19:47
* Define .node-version that can be read by multiple node.js version
  managers. Using the emerging standard: https://github.com/shadowspawn/node-version-usage
* .nvmrc is a superset of .node-version standard. It is safe to `ln -s .node-version .nvmrc`, but not vice versa.
  * For example, don't use special .nvmrc syntax/features inside .node-version.  If strict .node-version syntax
    is used, then it will work for .nvmrc
* package-lock.json: Updated to lockfileVersion 2 because npm is pinned
  to version 7. v2 unlocks the ability to do deterministic and
  reproducible builds.
* Upgraded:
  * @typescript-eslint/eslint-plugin
  * @typescript-eslint/parser
…se the interface has a generic and defining WorkflowParams with ConstructorParameters causes the generic argument to be lost.
@@ -18,7 +18,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [12.x]
node-version: [14.x]
Copy link
Owner Author

@dhilt dhilt Oct 5, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub said:

This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

This should help.

@stale
Copy link

stale bot commented Feb 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed within seven days if no further activity occurs. If it needs to remain open, add the "permanent" label.

@stale stale bot added the stale label Feb 19, 2022
@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically closed because it was stale.

@stale stale bot closed this Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants