r1.3

This release contains the definition and documentation of

• call-forwarding-signal v0.2.0

The API definition(s) are based on

• Commonalities v0.4.0
• Identity and Consent Management v0.2.0

call-forwarding-signal v0.2.0

This is the first official release of the Call Forwarding Signal API, version 0.2.0. It contains mainly alignments with the Commonalities 0.4.0 and the Release Management Guidelines.

• API definition with inline documentation:
  • OpenAPI YAML spec file
  • View it on ReDoc
  • View it on Swagger Editor

Because this is the first official release, in the following there is a full list of the features supported by the API, including the features listed in the previous release candidates.

What's New

• Support for the following use cases: Use Cases · camaraproject/CallForwardingSignal · Discussion #3 (github.com)
• Phone number retrieved from 3-legs access token: CAMARA Guidelines: Phone number identification with 3Legs · Issue #51 · camaraproject/CallForwardingSignal (github.com)
• Optional operation (/call-forwardings): Optional operations · Issue #37 · camaraproject/CallForwardingSignal (github.com)

Full Changelog: https://github.com/camaraproject/CallForwardingSignal/commits/r1.3

r1.2

This release contains the definition and documentation of

• call-forwarding-signal v0.2.0-rc.2

The API definition(s) are based on

• Commonalities v0.4.0-rc.1
• Identity and Consent Management v0.2.0-rc.2

call-forwarding-signal v0.2.0-rc.2

This is the second release candidate of the version 0.2.0. It contains mainly alignments with the Commonalities 0.4.0 and the Release Management Guidelines.

The pre-release is suitable for implementers, but it is not recommended to use the API with customers in productive environments.

• API definition with inline documentation:
  • OpenAPI YAML spec file
  • View it on ReDoc
  • View it on Swagger Editor

Added

Changed

• Improvement of user stories by @FabrizioMoggio in #86
• Aligned info.description Authorization and Authentication section with ICM 0.2.0 by @FabrizioMoggio in #91

Fixed

• Removed the version number in the ".feature" files in the "Background" section by @FabrizioMoggiom in #83
• Alignments within object description and fields by @FabrizioMoggio in #68

Removed

Full Changelog: r1.1...r1.2

r1.1

This is the first (pre) release candidate of the CAMARA CallForwardingSignal API

The version number for the YAML file is v0.2.0-rc.1

• API definition with inline documentation:
  • OpenAPI YAML spec file
  • View it on ReDoc
  • View it on Swagger Editor

Please note:

• This is an pre release candidate version, there are bug fixes to be expected and incompatible changes in upcoming versions
• The release is suitable for implementers, but it is not recommended to use the API with customers in productive environments
• Version numbers before v0.2.0-rc.1 were used during the development of this version but not released

What's New

• Support for the following use cases: Use Cases · camaraproject/CallForwardingSignal · Discussion #3 (github.com)
• Phone number retrieved from 3-legs access token: CAMARA Guidelines: Phone number identification with 3Legs · Issue #51 · camaraproject/CallForwardingSignal (github.com)
• Optional operation (/call-forwardings): Optional operations · Issue #37 · camaraproject/CallForwardingSignal (github.com)

New Contributors

• @FabrizioMoggio
• @bigludo7
• @rartych
• @StefanoFalsetto-CKHIOD
• @enlaichu
• @chinaunicomyangfan

Full Changelog: https://github.com/CallForwardingSignal/CallForwardingSignal/commits/r1.1