Update dependency standard to v1.32.1 #676
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.24.3
->1.32.1
Release Notes
standardrb/standard (standard)
v1.32.1
Compare Source
v1.32.0
Compare Source
v1.31.2
Compare Source
v1.31.1
Compare Source
v1.31.0
Compare Source
v1.30.1
Compare Source
Standard::PluginSupport
. Moving it toLintRoller::Support
to avoid circular dependencies between Standard Ruby and its plugins
v1.30.0
Compare Source
Standard::PluginSupport
module of classes designed to make it a littleeasier to author plugins.
MergesUpstreamMetadata#merge
will allow a minimalYAML config (say,
standard-sorbet
's, which only containsEnabled
values foreach rule) to merge in any other defaults from a source YAML (e.g.
rubocop-sorbet
's which includesDescription
,VersionAdded
, and so on).This way that metadata is neither absent at runtime nor duplicated in a standard
plugin that mirrors a rubocop extension
v1.29.0
Compare Source
v1.28.5
Compare Source
v1.28.4
Compare Source
v1.28.3
Compare Source
v1.28.2
Compare Source
v1.28.1
Compare Source
DisabledByDefault: true
inAllCops
Effectively, a single lint_roller plugin whose
rules
were of type:object
would inadvertently mark all previously-defined rules as invalid.
#557
v1.28.0
Compare Source
lint_roller plugins. See:
extend_config
that change the sameset of rules has been fixed to be first-in-wins, as opposed to last-in-wins.
This ensures a consistent behavior across plugins and extended configurations,
namely that the first thing to configure a given rule effectively locks it
from subsequent changes
DisabledByDefault: true
. This shouldn't impact anyone, but mightchange the behavior of some
extend_config
users. Because Standard specifiesevery rule in rubocop and rubocop-performance, this configuration's absence
wasn't felt until we went to the plugin system, where it makes much more sense
for plugins to opt-in to the cops they want to configure, as opposed to just
running every single one that they happen to load/require
v1.27.0
Compare Source
v1.26.0
Compare Source
--fix-unsafely
andrake standard:fix_unsafely
for runningunsafe corrections. Improve output about fix suggestions, as well
#545
v1.25.5
Compare Source
executeCommand
to prevent conflict withthe VS Code extension's client-side registration of the same name
#544
v1.25.4
Compare Source
#543
v1.25.3
Compare Source
rubocop
andrubocop-performance
to allowpatch-level updates
v1.25.2
Compare Source
isn't worth the inconsistency it causes and the fact it is incompatible with
ActiveSupport #527
v1.25.1
Compare Source
stdin
mode, don't invoke the RuboCop runner withparallel: true
toavoid an interaction that breaks auto-fixing
#530,
#536
v1.25.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10am every weekday,before 4pm every weekday" in timezone Europe/London.
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.