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: micronaut-projects/micronaut-core
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.8.6
Choose a base ref
...
head repository: micronaut-projects/micronaut-core
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.8.7
Choose a head ref
  • 11 commits
  • 9 files changed
  • 3 contributors

Commits on Mar 5, 2025

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

Commits on Mar 7, 2025

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

Commits on Mar 10, 2025

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

Commits on Mar 11, 2025

  1. fix compiler warning for unrecognised options (#11648)

    Currently the following warnings are being printed when compiling with Micronaut
    
    ```
    warning: The following options were not recognized by any processor: '[micronaut.processing.internal.warnings]'
    1 warning
    
    warning: The following options were not recognized by any processor: '[micronaut.processing.internal.warnings]'
    ```
    
    This regression was introduced by 51e35b1
    
    Which didn't return `getSupportedOptions()` for the new annotation processor argument.
    graemerocher authored Mar 11, 2025
    Configuration menu
    Copy the full SHA
    cdb5cf3 View commit details
    Browse the repository at this point in the history
  2. fix introduction advise skipping methods of generated super interfaces (

    #11652)
    
    previously super interfaces were filtered out if there were errors but the correct thing to do is throw `ElementPostponedToNextRoundException` on first access. In addition BeanDefinitionInjectProcessor was not handling `ElementPostponedToNextRoundException` so exceptions thrown during bean definition processing did not cause a retry on the second round. Ideally we should get rid of the non-public `PostponeToNextRoundException` at some point.
    graemerocher authored Mar 11, 2025
    Configuration menu
    Copy the full SHA
    dd1e0f7 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    e23ed6a View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    3f3b152 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    00c827c View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    e10e0cf View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    4531b5e View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    6d76a8e View commit details
    Browse the repository at this point in the history
Loading