Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: apache/maven-release
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: maven-release-3.3.0
Choose a base ref
...
head repository: apache/maven-release
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: maven-release-3.3.1
Choose a head ref
  • 4 commits
  • 7 files changed
  • 3 contributors

Commits on Nov 30, 2025

  1. Configuration menu
    Copy the full SHA
    c8613d2 View commit details
    Browse the repository at this point in the history

Commits on Dec 4, 2025

  1. Bump org.codehaus.plexus:plexus-testing from 2.0.1 to 2.0.2 (#1444)

    Bumps [org.codehaus.plexus:plexus-testing](https://github.com/codehaus-plexus/plexus-testing) from 2.0.1 to 2.0.2.
    - [Release notes](https://github.com/codehaus-plexus/plexus-testing/releases)
    - [Commits](codehaus-plexus/plexus-testing@plexus-testing-2.0.1...plexus-testing-2.0.2)
    
    ---
    updated-dependencies:
    - dependency-name: org.codehaus.plexus:plexus-testing
      dependency-version: 2.0.2
      dependency-type: direct:development
      update-type: version-update:semver-patch
    ...
    
    Signed-off-by: dependabot[bot] <support@github.com>
    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    dependabot[bot] authored Dec 4, 2025
    Configuration menu
    Copy the full SHA
    2a82901 View commit details
    Browse the repository at this point in the history

Commits on Dec 9, 2025

  1. Revert inclusion of ci skip in release commit msg

    This reverts PR #1423 which added the ci skip text into the default
    release commit.  This broke many developers workflows because it pushes
    a choice about CI/CD process into default configuration.  If developers
    genuinely want to skip CI/CD for the release commit then they already
    had configuration to override the commit message and inject the
    necessary ci skip text.  However, the maven-release-plugin itself should
    not make any assumptions about developers CI/CD setups, nor do anything
    by default that might cause those to skip release commit builds that
    developers might be relying upon.
    rvesse authored and kwin committed Dec 9, 2025
    Configuration menu
    Copy the full SHA
    f0f28e5 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    7e8ebac View commit details
    Browse the repository at this point in the history
Loading