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

chore(deps): bump table from 6.0.4 to 6.0.7 #12324

Merged
merged 1 commit into from
Jan 4, 2021

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps table from 6.0.4 to 6.0.7.

Release notes

Sourced from table's releases.

v6.0.7

6.0.7 (2021-01-04)

Bug Fixes

  • a bug cause singleLine rendering failed (#133) (bfa415e)

v6.0.6

6.0.6 (2021-01-02)

Bug Fixes

  • update all dependencies (5c5a09d)

v6.0.5

6.0.5 (2021-01-02)

Bug Fixes

Commits

Dependabot compatibility score

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 readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

  • Update frequency
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

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>
@gitpod-io
Copy link

gitpod-io bot commented Jan 4, 2021

@dependabot-preview 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
@mergify
Copy link
Contributor

mergify bot commented Jan 4, 2021

Thanks Dependabot!

@mergify mergify bot merged commit 6c4d4f8 into master Jan 4, 2021
@mergify mergify bot deleted the dependabot/npm_and_yarn/table-6.0.7 branch January 4, 2021 06:22
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: 7cda791
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant