-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(deps): bump table from 6.0.4 to 6.0.7 #12324
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [table](https://github.com/gajus/table) from 6.0.4 to 6.0.7. - [Release notes](https://github.com/gajus/table/releases) - [Commits](gajus/table@v6.0.4...v6.0.7) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
dependabot-preview
bot
added
the
dependencies
This issue is a problem in a dependency or a pull request that updates a dependency file.
label
Jan 4, 2021
Thanks Dependabot! |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
rix0rrr
added a commit
that referenced
this pull request
Jan 4, 2021
We were passing (by mistake) an unrecognized property to the `table` module. This didn't use to be a problem, but the `table` module has suddenly started throwing an "invalid config" error. The cause is a dependency update that happened today. * In #12324, the version of `table` was updated from `6.0.4` to `6.0.7`. * In [6.0.5](https://github.com/gajus/table/releases/tag/v6.0.5), `table` changes the way it does JSON validation of the input configuration ob ject. Didn't dive into all of the changes, but it stands to reason the validator has become more strict and where it *used* to allow additional properties (probably by accident) it no longer does so. Undo the passing of the unused property. This change is a **chore** instead of a **fix** because the change wasn't released yet.
mergify bot
pushed a commit
that referenced
this pull request
Jan 4, 2021
We were passing (by mistake) an unrecognized property to the `table` module. This didn't use to be a problem, but the `table` module has suddenly started throwing an "invalid config" error. The cause is a dependency update that happened today. * In #12324, the version of `table` was updated from `6.0.4` to `6.0.7`. * In [6.0.5](https://github.com/gajus/table/releases/tag/v6.0.5), `table` changes the way it does JSON validation of the input configuration ob ject. Didn't dive into all of the changes, but it stands to reason the validator has become more strict and where it *used* to allow additional properties (probably by accident) it no longer does so. Undo the passing of the unused property. This change is a **chore** instead of a **fix** because the change wasn't released yet. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
flochaz
pushed a commit
to flochaz/aws-cdk
that referenced
this pull request
Jan 5, 2021
Bumps [table](https://github.com/gajus/table) from 6.0.4 to 6.0.7. - [Release notes](https://github.com/gajus/table/releases) - [Commits](gajus/table@v6.0.4...v6.0.7) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
flochaz
pushed a commit
to flochaz/aws-cdk
that referenced
this pull request
Jan 5, 2021
We were passing (by mistake) an unrecognized property to the `table` module. This didn't use to be a problem, but the `table` module has suddenly started throwing an "invalid config" error. The cause is a dependency update that happened today. * In aws#12324, the version of `table` was updated from `6.0.4` to `6.0.7`. * In [6.0.5](https://github.com/gajus/table/releases/tag/v6.0.5), `table` changes the way it does JSON validation of the input configuration ob ject. Didn't dive into all of the changes, but it stands to reason the validator has become more strict and where it *used* to allow additional properties (probably by accident) it no longer does so. Undo the passing of the unused property. This change is a **chore** instead of a **fix** because the change wasn't released yet. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
This issue is a problem in a dependency or a pull request that updates a dependency file.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps table from 6.0.4 to 6.0.7.
Release notes
Sourced from table's releases.
Commits
bfa415e
fix: a bug cause singleLine rendering failed (#133)23f9947
chore: add package-lock to gitignore (#132)91a462e
docs: generate docs0c3453a
docs: remove broken GitSpo referencefb88732
docs: generate docs5c5a09d
fix: update all dependencies645060e
fix: migrate to ajv v7 (#130)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in the
.dependabot/config.yml
file in this repo: