Skip to content

Removing the lint roller gemfile.lock in knife habitat package - #59

Merged
nikhil2611 merged 4 commits into
mainfrom
nikhil/lint_roller_fix
Jan 29, 2026
Merged

Removing the lint roller gemfile.lock in knife habitat package #59
nikhil2611 merged 4 commits into
mainfrom
nikhil/lint_roller_fix

Conversation

@nikhil2611

Copy link
Copy Markdown
Contributor

Description

Removing the lint roller gemfile.lock in knife habitat package

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.

Signed-off-by: nikhil2611 <ngupta@progress.com>
Signed-off-by: nikhil2611 <ngupta@progress.com>
- Moved cleanup_lint_roller.rb to scripts/ directory
- Updated plan.sh to set GEM_HOME to vendor/ruby/3.4.0 before cleanup
- Updated plan.ps1 to set GEM_HOME to correct ruby version path
- This ensures Gem::Specification can find lint_roller gem installed by bundler
- No impact on other build functions as GEM_HOME is reset in do_install

Signed-off-by: nikhil2611 <ngupta@progress.com>
Signed-off-by: nikhil2611 <ngupta@progress.com>
@nikhil2611
nikhil2611 force-pushed the nikhil/lint_roller_fix branch from 6d02cfa to 21f0e23 Compare January 29, 2026 12:32
@nikhil2611
nikhil2611 merged commit 3122bb7 into main Jan 29, 2026
27 checks passed
@nikhil2611
nikhil2611 deleted the nikhil/lint_roller_fix branch January 29, 2026 14:25
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