search

shipwright-io / triggers

Event-driven Shipwright Builds
Apache License 2.0
6 stars 7 forks source link

Bump github.com/onsi/ginkgo/v2 from 2.4.0 to 2.6.0 #11

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/onsi/ginkgo/v2 from 2.4.0 to 2.6.0.

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

v2.6.0

2.6.0

Features

  • ReportBeforeSuite provides access to the suite report before the suite begins.
  • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
  • Add support to customize junit report config to omit spec labels (#1087) [de44005]

Fixes

  • Fix stack trace pruning so that it has a chance of working on windows [2165648]

v2.5.1

2.5.1

Fixes

  • skipped tests only show as 'S' when running with -v [3ab38ae]
  • Fix typo in docs/index.md (#1082) [55fc58d]
  • Fix typo in docs/index.md (#1081) [8a14f1f]
  • Fix link notation in docs/index.md (#1080) [2669612]
  • Fix typo in --progress deprecation message (#1076) [b4b7edc]

Maintenance

  • chore: Included githubactions in the dependabot config (#976) [baea341]
  • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

v2.5.0

2.5.0

Ginkgo output now includes a timeline-view of the spec

This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

Features

... (truncated)

Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

2.6.0

Features

  • ReportBeforeSuite provides access to the suite report before the suite begins.
  • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
  • Add support to customize junit report config to omit spec labels (#1087) [de44005]

Fixes

  • Fix stack trace pruning so that it has a chance of working on windows [2165648]

2.5.1

Fixes

  • skipped tests only show as 'S' when running with -v [3ab38ae]
  • Fix typo in docs/index.md (#1082) [55fc58d]
  • Fix typo in docs/index.md (#1081) [8a14f1f]
  • Fix link notation in docs/index.md (#1080) [2669612]
  • Fix typo in --progress deprecation message (#1076) [b4b7edc]

Maintenance

  • chore: Included githubactions in the dependabot config (#976) [baea341]
  • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

2.5.0

Ginkgo output now includes a timeline-view of the spec

This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

Features

  • Provide details about which timeout expired [0f2fa27]

Fixes

... (truncated)

Commits
  • 6ad4fae v2.6.0
  • 366815d fix race in internal integration spec
  • 1869212 Refactor and clean up ReportBeforeSuite additions.
  • 52b4b9c ReportBeforeSuite provides the suite report before the suite begins
  • 2165648 Fix stack trace pruning so that it has a chance of working on windows
  • 956e6d2 Add junit config option for omitting leafnodetype (#1088)
  • 8804859 Fix typo in docs (#1089)
  • de44005 Add support to customize junit report config to omit spec labels (#1087)
  • a3eed17 v2.5.1
  • 3ab38ae skipped tests only show as 'S' when running with -v
  • Additional commits viewable in compare view


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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
openshift-ci[bot] commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], SaschaSchwarze0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/shipwright-io/triggers/blob/main/OWNERS)~~ [SaschaSchwarze0] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment