Skip to content

APICompat doesn't capture all changes that might happen during servicing #84142

@ericstj

Description

@ericstj

Description

#84031 represents a regression in servicing that we could have caught with API Compat.

We should consider the following new APICompat comparisons:

  1. Servicing branch to future framework / packages.
  2. Current branch to previous serviced packages (don't limit the baseline to GA). This will catch things after they ship, but will catch them before our customers do.
  3. Consider enabling strict mode in servicing for all packages. Determine an assembly version rule that might be acceptable in this case but not too noisy.

Reproduction Steps

Make a breaking change in servicing that makes a serviced package incompatible with a newer version of that package.

Expected behavior

APICompat catches this and raises an error.

Actual behavior

No error was raised.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions