Skip to content

Update dependency openscap to "~>0.6.0" - #23642

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

Update dependency openscap to "~>0.6.0"#23642
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/openscap-0.x

Conversation

@renovate

@renovate renovate Bot commented Oct 29, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
openscap "~>0.4.8""~>0.6.0" age adoption passing confidence

Release Notes

isimluk/ruby-openscap (openscap)

v0.6.0

Compare Source

v0.5.2

Compare Source

v0.5.1

Compare Source

v0.5.0

Compare Source


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 becomes conflicted, 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 Fryguy as a code owner October 29, 2025 17:43
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from 553ea4e to e967943 Compare November 18, 2025 23:31
@Fryguy Fryguy closed this Nov 19, 2025
@Fryguy Fryguy reopened this Nov 19, 2025
@Fryguy

Fryguy commented Nov 19, 2025

Copy link
Copy Markdown
Member

openscap 6.0.0 dropped support for Ruby 3.2, so this fails on Ruby 3.1 - we can probably bump to 0.5.2 though

@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from e967943 to 12193a1 Compare December 31, 2025 18:40
@Fryguy

Fryguy commented Jan 16, 2026

Copy link
Copy Markdown
Member

Since we don't support Ruby < 3.3 anymore, we can now merge this.

@isimluk Hi 👋 - just a heads up that you forgot to push the v0.6.0 tag for ruby-openscap in GitHub, even though it was released.

@isimluk

isimluk commented Jan 26, 2026

Copy link
Copy Markdown
Member

Since we don't support Ruby < 3.3 anymore, we can now merge this.

@isimluk Hi 👋 - just a heads up that you forgot to push the v0.6.0 tag for ruby-openscap in GitHub, even though it was released.

Thank You. I stand corrected.

@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from 12193a1 to 2a6ff2a Compare February 2, 2026 15:49
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from 2a6ff2a to 0af0cfd Compare February 12, 2026 12:29
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from 0af0cfd to d468fb2 Compare March 13, 2026 12:56
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from d468fb2 to 50d5087 Compare May 18, 2026 13:49
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch 2 times, most recently from 169e52f to fbe090d Compare July 20, 2026 20:28
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from fbe090d to 53a3b63 Compare August 12, 2026 02:42
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch 2 times, most recently from 748616d to c99206e Compare September 2, 2026 18:37
@renovate
renovate Bot force-pushed the renovate/openscap-0.x branch from c99206e to 20fa83c Compare September 3, 2026 17:59
@miq-bot

miq-bot commented Sep 3, 2026

Copy link
Copy Markdown
Member

Checked commit 20fa83c with ruby 3.3.12, rubocop 1.89.0, haml-lint 0.78.0, and yamllint 1.37.1
1 file checked, 0 offenses detected
Everything looks fine. ⭐

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants