mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-26 07:20:39 +00:00
Jamie Tanna
e0a77f8121
While looking at the fix for `actions/setup-java`, we noticed that the `ruby/setup-ruby` may also be affected, as it notes: > short version like '2.6', automatically using the latest release > matching that version As Ruby versioning treats `3.4` as a pinned version rather than a range, we'd propose a patch upgrade rewriting it to `3.4.7`, losing the rolling behaviour the workflow asked for. We can reuse the `semver-partial` handling as a `partialValSchema` helper, so short versions keep their precision and only exact versions are looked up as pinned. Co-authored-by: Claude Opus 5 <jamie.tanna+claude-code@mend.io>
15 lines
562 B
TypeScript
15 lines
562 B
TypeScript
import { RubyVersionDatasource } from '../../../datasource/ruby-version/index.ts';
|
|
import type { KnownActionConfig } from '../types.ts';
|
|
import { partialValSchema } from './utils.ts';
|
|
|
|
export const rubyVersionActions: Record<string, KnownActionConfig> = {
|
|
// https://github.com/ruby/setup-ruby
|
|
'ruby/setup-ruby': {
|
|
datasource: RubyVersionDatasource.id,
|
|
packageName: 'ruby',
|
|
// a short `ruby-version` such as `3.3` means the latest release matching
|
|
// it, rather than a pinned version
|
|
withSchema: partialValSchema('ruby-version'),
|
|
},
|
|
};
|