Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/strm 1259 #4

Merged
merged 4 commits into from
Jul 12, 2022
Merged

Feature/strm 1259 #4

merged 4 commits into from
Jul 12, 2022

Conversation

bobvandenhoogen
Copy link
Contributor

No description provided.

@ivan-p92
Copy link

ivan-p92 commented Jul 6, 2022

LGTM. Just a general comment: should we use keycloak at all in naming? We have abstracted it away, so we don't need to "expose" our implementation per se.

@bobvandenhoogen bobvandenhoogen merged commit 19212c0 into master Jul 12, 2022
@bobvandenhoogen bobvandenhoogen deleted the feature/strm-1259 branch July 12, 2022 13:12
github-actions bot pushed a commit that referenced this pull request Jul 12, 2022
# [3.0.0](v2.0.2...v3.0.0) (2022-07-12)

* Feature/strm 1259 (#4) ([19212c0](19212c0)), closes [#4](#4)

### BREAKING CHANGES

* authentication has changed
@strmprivacy-io
Copy link

🎉 This PR is included in version 3.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants