Skip to content

Conversation

@johnmccrae
Copy link

Description

Creating a stable branch for Inspec 5

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

@johnmccrae johnmccrae closed this Apr 30, 2025
@johnmccrae johnmccrae reopened this Apr 30, 2025
Signed-off-by: John McCrae <[email protected]>
@johnmccrae johnmccrae force-pushed the jfm/inspec-ruby-3-plus branch from f2d4bc3 to a8289e6 Compare April 30, 2025 22:38
@johnmccrae johnmccrae merged commit 65a6059 into Ruby30-Stable Apr 30, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants