Repository navigation
chore(release): version packages - #68
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 10, 2026 01:38
44cf3ac to
10c568d
Compare
nkavian
force-pushed
the
changeset-release/main
branch
from
November 10, 2026 01:45
10c568d to
c78158a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 10, 2026 01:47
c78158a to
1aecb9a
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@aep-foundation/agent@0.7.1
Patch Changes
#69
86c6ae9Thanks @nkavian! - Accept complete opaque API-key header values, including Service-supplied authentication prefixes and internal spaces. Preserve the issued value and header without adding or removing a prefix, while rejecting unsafe field values.Accept case-insensitive OAuth Bearer token types without changing access tokens.
Allow empty Basic usernames, passwords, and realms while requiring username and password fields to be present strings.
Verify API-key values through the configured credential handlers instead of rejecting Bearer or Basic prefixes as unsupported grant types. Reject requests that match multiple session credentials.
Updated dependencies [
86c6ae9]:@aep-foundation/conformance@0.6.1
Patch Changes
#69
86c6ae9Thanks @nkavian! - Accept complete opaque API-key header values, including Service-supplied authentication prefixes and internal spaces. Preserve the issued value and header without adding or removing a prefix, while rejecting unsafe field values.Accept case-insensitive OAuth Bearer token types without changing access tokens.
Allow empty Basic usernames, passwords, and realms while requiring username and password fields to be present strings.
Verify API-key values through the configured credential handlers instead of rejecting Bearer or Basic prefixes as unsupported grant types. Reject requests that match multiple session credentials.
#67
3181632Thanks @nkavian! - Synchronize bundled specification artifacts and test-vector validation with core draft 05, published documentation, and the Service Documents example link.Updated dependencies [
86c6ae9]:@aep-foundation/core@0.8.1
Patch Changes
#69
86c6ae9Thanks @nkavian! - Accept complete opaque API-key header values, including Service-supplied authentication prefixes and internal spaces. Preserve the issued value and header without adding or removing a prefix, while rejecting unsafe field values.Accept case-insensitive OAuth Bearer token types without changing access tokens.
Allow empty Basic usernames, passwords, and realms while requiring username and password fields to be present strings.
Verify API-key values through the configured credential handlers instead of rejecting Bearer or Basic prefixes as unsupported grant types. Reject requests that match multiple session credentials.
@aep-foundation/service@0.5.1
Patch Changes
#69
86c6ae9Thanks @nkavian! - Accept complete opaque API-key header values, including Service-supplied authentication prefixes and internal spaces. Preserve the issued value and header without adding or removing a prefix, while rejecting unsafe field values.Accept case-insensitive OAuth Bearer token types without changing access tokens.
Allow empty Basic usernames, passwords, and realms while requiring username and password fields to be present strings.
Verify API-key values through the configured credential handlers instead of rejecting Bearer or Basic prefixes as unsupported grant types. Reject requests that match multiple session credentials.
Updated dependencies [
86c6ae9]: