Releases: sting-ioc/sting
Releases · sting-ioc/sting
Release list
v0.40
Changes in this release:
- Update the
org.realityforge.protonartifacts to version0.75. - Add a suppressible warning for redundant singleton
@Typedannotations that only restate the default published type. - Rely on Proton to declare common annotation processor options while continuing to declare Sting-specific descriptor
and graph report options.
v0.39
Changes in this release:
- Migrate
sting-servertransaction support fromjavax.transactiontojakarta.transaction-api2.0.1.
v0.38
The release includes 13 non breaking API changes.
Changes in this release:
- Add compile-time service-interface interceptors under
sting.interceptors, including lifecycle interceptors,
graph/report integration, runtime proxy wiring, documentation, and test coverage. - Add enum-backed
{memberName}templates for@InterceptorBinding.implementedBy, resolving selected enum values to
PascalCase interceptor implementation class names at compile time. - Add the
sting-serverartifact with a JTA-backed@Transactionalinterceptor binding for Sting service-interface
transaction boundaries.
v0.37
Changes in this release:
- Update the
org.realityforge.braincheckartifacts to version1.33.0.
v0.36
Changes in this release:
- Update the
org.realityforge.protonartifacts to version0.72.
v0.35
Changes in this release:
- Update the
org.realityforge.protonartifacts to version0.71and use Proton's shaded
generated-source formatting support from the Sting processor.
v0.34
The release includes 2 non breaking API changes.
Changes in this release:
- Add validation-only
@ActAsStingConsumerand@ActAsStingProviderintegration hooks, redefine
@ActAsStingComponentas their union, and stop treating@StingProvideras a validation escape
hatch for@Named,@Typed, and@Eageron framework-managed types. - Clarify the documentation for provider-backed framework integration so it distinguishes explicit
include aliasing from auto-discovery, and explains when@Eager,@Named, and@Typedon
framework-managed types need to be copied onto the resolved Sting provider.
v0.33
Changes in this release:
- Explicitly document the expectations for
@StingProvidertypes that contain@Eager,@Namedand@Typedannotations. - Explicitly document and add integration tests to ensure that
@Typedannotations can appear on provider methods of fragments.
v0.32
Changes in this release:
v0.31
Changes in this release:
Changes in this release:
- Trigger
StingProcessorfor all public Sting annotations, including@StingProviderand
@ActAsStingComponent, and align processor docs/Javadocs around the exact placements where each annotation is
actively processed, tolerated for integration, or rejected. - Tighten annotation validation so
@Named,@Typed, and@Eagerare rejected on framework component types
annotated with annotations meta-annotated by@StingProvider. These annotations must be applied to the resolved
Sting provider type instead. - Tighten annotation validation so
@Typedis rejected on@Injectoroutput methods rather than being accepted
and ignored. - Upgrade the
org.realityforge.protonartifact to version0.69. - Migrate
javapoettocom.palantir.javapoet:javapoet:jar:0.14.0which is still maintained.