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

Automatically update all Manifest files #104

Merged
merged 1 commit into from
Nov 10, 2019
Merged

Automatically update all Manifest files #104

merged 1 commit into from
Nov 10, 2019

Conversation

DilumAluthge
Copy link
Member

@DilumAluthge DilumAluthge commented Nov 10, 2019

Closes #102

This is an expanded version of the excellent work by @christopher-dG in #102. This PR adds the following on top of the work in #102:

  1. Adds tests.
  2. Makes sure that we support custom registries.
  3. Run jobs in a "sandbox" that does not have access to most environment variables. That way, if a package has a malicious build step, for example, they cannot steal your GitHub token.

I have been thinking about this, and it makes sense that "update all Manifests" should be the default behavior. After all, Dependabot will update your package.json and package-lock.json files by default. So we should do the same thing. It is easy enough to disable this default behavior by passing a no-op function () -> () as the first positional argument to CompatHelper.main.

That being said, because we are changing the default behavior, this is a breaking change.

@DilumAluthge DilumAluthge self-assigned this Nov 10, 2019
@DilumAluthge
Copy link
Member Author

bors merge=@DilumAluthge,@christopher-dG

bors bot pushed a commit that referenced this pull request Nov 10, 2019
104: Automatically update all Manifest files r=DilumAluthge,christopher-dG a=DilumAluthge

Closes #102 

This is an expanded version of the excellent work by @christopher-dG in #102. This PR adds the following on top of the work in #102:
1. Adds tests.
2. Makes sure that we support custom registries.
3. Run jobs in a "sandbox" that does not have access to most environment variables. That way, if a package has a malicious build step, for example, they cannot steal your GitHub token.

Co-authored-by: Dilum Aluthge <[email protected]>
@bors
Copy link
Contributor

bors bot commented Nov 10, 2019

Build failed

  • continuous-integration/travis-ci/push

@DilumAluthge
Copy link
Member Author

bors merge=@DilumAluthge,@christopher-dG

bors bot pushed a commit that referenced this pull request Nov 10, 2019
104: Automatically update all Manifest files r=DilumAluthge,christopher-dG a=DilumAluthge

Closes #102 

This is an expanded version of the excellent work by @christopher-dG in #102. This PR adds the following on top of the work in #102:
1. Adds tests.
2. Makes sure that we support custom registries.
3. Run jobs in a "sandbox" that does not have access to most environment variables. That way, if a package has a malicious build step, for example, they cannot steal your GitHub token.

---

I have been thinking about this, and it makes sense that "update all Manifests" should be the default behavior. After all, Dependabot will update your `package.json` and `package-lock.json` files by default. So we should do the same thing. It is easy enough to disable this default behavior by passing a no-op function `() -> ()` as the first positional argument to `CompatHelper.main`.

That being said, because we are changing the default behavior, this is a breaking change.

Co-authored-by: Dilum Aluthge <[email protected]>
@bors
Copy link
Contributor

bors bot commented Nov 10, 2019

Build succeeded

@bors bors bot merged commit 8cf3360 into master Nov 10, 2019
@bors bors bot deleted the da/update_manifests branch November 10, 2019 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant