Permalink
base repository: diffplug/spotless-cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
base: main
Choose a base ref
...
head repository: diffplug/spotless-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
compare: bugfix/make-sure-to-include-usage-help-after-release
Choose a head ref
  • 3 commits
  • 2 files changed
  • 1 contributor

Commits on Jun 4, 2025

  1. chore(ci): manually publish chocolatey source 

    as the jreleaser publish action somehow skips this step, we manually
perform it after the fact.

Reason for why this is skipped on jreleaser workflow is unknown, but it
most probably is due to a configuration mistake on my end.
    @simschla
    simschla committedJun 4, 2025
    Configuration menu
    Copy the full SHA
    e5e1c3bView commit details
    Browse the repository at this point in the history

  2. fixup! chore(ci): manually publish chocolatey source

    @simschla
    simschla committedJun 4, 2025
    Configuration menu
    Copy the full SHA
    2d19bbbView commit details
    Browse the repository at this point in the history

  3. fix(ci): make sure to generateUsage help files before triggering build 

    this makes sure that when README.md is updated with latest version
number(s), there is also an up-to-date collection of usage help files
available. This is required, because even when using a dependency to
`generateUsage` task, the config phase of spotlessMarkdownApply has
already picked up the empty/non-existing files, even though they would
be available when the task is actually run...
so by generating the files before hand, we make sure they are available
in config phase of spotlessMarkdownApply.
    @simschla
    simschla committedJun 4, 2025
    Configuration menu
    Copy the full SHA
    5cddc51View commit details
    Browse the repository at this point in the history
Loading