Skip to content

chore(deps): update dependency rspec_junit_formatter to v0.8.0 - #375

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rspec_junit_formatter-0.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rspec_junit_formatter-0.x

Conversation

@renovate

@renovate renovate Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
rspec_junit_formatter (changelog) 0.6.0 → 0.8.0 age confidence

Release Notes

sj26/rspec_junit_formatter (rspec_junit_formatter)

v0.8.0

Compare Source

Added
  • Use GitLab, CircleCI, Semaphore, Buildkite and Bitbucket parallel worker labels in XML suite names when TEST_ENV_NUMBER is unset (#​102). Keep native indexes, explicit TEST_ENV_NUMBER overrides (including empty), and the unsuffixed rspec default. Output filenames are unchanged; see parallel tests for precedence and nested-worker naming.

v0.7.1

Compare Source

Fixed
  • Transcode failure messages to UTF-8 before stripping RSpec diff colors, replacing invalid bytes and undefined conversions with U+FFFD (�) instead of crashing (#​113).
  • Strip trailing spaces from ordinary and aggregate failure detail lines, preserving indentation and internal spaces (#​125).

v0.7.0

Compare Source

Changed
  • Require Ruby >= 3.3 and RSpec >= 3.13, < 4. Ruby 3.3 remains supported during upstream security maintenance; Ruby 3.2 and earlier are end-of-life. RSpec 3.13 is the maintained stable minor series; RSpec 4 prereleases are not supported. See the support policy and upgrade instructions.
  • Test Ruby 3.3, 3.4 and 4.0 with both the locked development bundle and the RSpec 3.13 Appraisal.
  • Use 0.6.2 if you must keep an older Ruby or RSpec: pin gem "rspec_junit_formatter", "0.6.2", require: false and run bundle update rspec_junit_formatter. The RSpec dependency floor prevents older RSpec projects on newer Ruby from selecting 0.7.0.
Removed
  • Remove the RSpec 2 formatter, obsolete RSpec 3 compatibility fallbacks, and Appraisals for unmaintained RSpec versions. Formatting behavior on supported versions is unchanged.
Fixed
  • Create GitHub draft releases without looking them up through the published-release-by-tag endpoint (#​120).

v0.6.2

Compare Source

Changed
  • Require Ruby >= 3.3 and RSpec >= 3.13, < 4. Ruby 3.3 remains supported during upstream security maintenance; Ruby 3.2 and earlier are end-of-life. RSpec 3.13 is the maintained stable minor series; RSpec 4 prereleases are not supported. See the support policy and upgrade instructions.
  • Test Ruby 3.3, 3.4 and 4.0 with both the locked development bundle and the RSpec 3.13 Appraisal.
  • Use 0.6.2 if you must keep an older Ruby or RSpec: pin gem "rspec_junit_formatter", "0.6.2", require: false and run bundle update rspec_junit_formatter. The RSpec dependency floor prevents older RSpec projects on newer Ruby from selecting 0.7.0.
Removed
  • Remove the RSpec 2 formatter, obsolete RSpec 3 compatibility fallbacks, and Appraisals for unmaintained RSpec versions. Formatting behavior on supported versions is unchanged.
Fixed
  • Create GitHub draft releases without looking them up through the published-release-by-tag endpoint (#​120).

v0.6.1

Compare Source

This is the final legacy-compatible release. It retains Ruby >= 2.3 and RSpec >= 2, < 4 (except 2.12.0), including the aggregate failure fix from 0.6.1. Projects staying on Ruby < 3.3 or RSpec < 3.13 should pin gem "rspec_junit_formatter", "0.6.2" before the next release raises those minimum versions. Permitted versions are not all tested; see the compatibility table.

Fixed
  • Replace invalid byte sequences and undefined UTF-8 conversions with U+FFFD (�) in XML escaping (#​105, #​116). This does not fix encoding errors before XML escaping, including #​113, or malformed backtraces rejected by RSpec.
Changed
  • Refresh the development bundle and test current RSpec on Ruby 3.4 and 4.0, without changing runtime requirements.
  • Publish unsigned, validated gem artifacts through approved GitHub Actions and RubyGems trusted publishing (#​117).
  • Check for GitHub Actions updates weekly with Dependabot (#​106).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 21, 2026 01:45
@renovate renovate Bot added dependencies Pull requests that update a dependency file renovate labels Oct 21, 2026
@renovate renovate Bot changed the title chore(deps): update dependency rspec_junit_formatter to v0.6.1 chore(deps): update dependency rspec_junit_formatter to v0.7.0 Oct 21, 2026
@renovate
renovate Bot force-pushed the renovate/rspec_junit_formatter-0.x branch from fa69375 to e163dd1 Compare October 21, 2026 04:59
@renovate renovate Bot changed the title chore(deps): update dependency rspec_junit_formatter to v0.7.0 chore(deps): update dependency rspec_junit_formatter to v0.7.1 Oct 21, 2026
@renovate
renovate Bot force-pushed the renovate/rspec_junit_formatter-0.x branch from e163dd1 to 3e7e949 Compare October 21, 2026 10:58
@renovate renovate Bot changed the title chore(deps): update dependency rspec_junit_formatter to v0.7.1 chore(deps): update dependency rspec_junit_formatter to v0.8.0 Oct 21, 2026
@renovate
renovate Bot force-pushed the renovate/rspec_junit_formatter-0.x branch from 3e7e949 to 93ecfb2 Compare October 21, 2026 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

0 participants