clients
clients copied to clipboard
bitwarden
[PM-13804] Add new Is-Beta header to requests
đī¸ Tracking
https://bitwarden.atlassian.net/browse/PM-13804
đ Objective
We want the ability to control feature flags based on whether the requesting client is a beta build or not.
To provide this context to LaunchDarkly, we must introduce a way for the clients to communicate that they are a beta to the server, where it can be used to build the LaunchDarkly context.
This will be done with an Is-Beta header on the request.
This PR adds that header to all API requests to our back-end based on whether the client-side betaBuild flag is enabled.
â° Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
đĻŽ Reviewer guidelines
- đ (
:+1:) or similar for great changes - đ (
:memo:) or âšī¸ (:information_source:) for notes or general info - â (
:question:) for questions - đ¤ (
:thinking:) or đ (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - đ¨ (
:art:) for suggestions / improvements - â (
:x:) or â ī¸ (:warning:) for more significant problems or concerns needing attention - đą (
:seedling:) or âģī¸ (:recycle:) for future improvements or indications of technical debt - â (
:pick:) for minor or nitpick changes
Codecov Report
Attention: Patch coverage is 0% with 30 lines in your changes missing coverage. Please review.
Project coverage is 33.25%. Comparing base (
97e195c) to head (3427ea7). Report is 198 commits behind head on main.
:white_check_mark: All tests successful. No failed tests found.
| Files with missing lines | Patch % | Lines |
|---|---|---|
| libs/common/src/services/api.service.ts | 0.00% | 30 Missing :warning: |
Additional details and impacted files
@@ Coverage Diff @@
## main #11605 +/- ##
==========================================
+ Coverage 33.20% 33.25% +0.05%
==========================================
Files 2782 2789 +7
Lines 86484 86675 +191
Branches 16484 16507 +23
==========================================
+ Hits 28714 28826 +112
- Misses 55483 55554 +71
- Partials 2287 2295 +8
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}
Checkmarx One â Scan Summary & Details â b89321c2-e0b0-4cad-9ffb-7b9065bce382
New Issues
| Severity | Issue | Source File / Package | Checkmarx Insight |
|---|---|---|---|
 |
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.ts: 63 | Attack Vector |
|
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.ts: 63 | Attack Vector |
|
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.ts: 63 | Attack Vector |
|
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.ts: 63 | Attack Vector |
|
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.html: 11 | Attack Vector |
|
Client_Privacy_Violation | /apps/web/src/app/vault/individual-vault/password-history.component.html: 11 | Attack Vector |
|
Missing_HSTS_Header | /libs/common/src/services/api.service.ts: 228 | Attack Vector |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 122 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 515 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 48 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 82 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 267 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 359 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 245 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 247 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 367 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 180 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 187 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 181 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1293 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-cli.yml: 405 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 194 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 35 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /retrieve-current-desktop-rollout.yml: 23 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 507 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 891 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 342 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 104 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /brew-bump-desktop.yml: 26 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1339 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 162 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 499 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 141 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 523 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 191 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /staged-rollout-desktop.yml: 29 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 288 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 408 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 201 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-web.yml: 44 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 196 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 41 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-auto-bump.yml: 21 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 297 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 297 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
 |
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 180 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 141 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 48 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /retrieve-current-desktop-rollout.yml: 23 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 245 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-cli.yml: 405 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 523 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 187 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1339 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 515 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 891 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-web.yml: 44 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 408 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 196 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 499 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 288 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 201 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 82 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 104 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 194 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 247 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 507 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 181 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 122 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 359 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1293 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 367 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 297 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 162 | Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps... |
Fixed Issues
| Severity | Issue | Source File / Package |
|---|---|---|
|
Client_Privacy_Violation | /libs/vault/src/components/password-history-view/password-history-view.component.html: 6 |
|
Client_Privacy_Violation | /libs/vault/src/components/password-history-view/password-history-view.component.html: 6 |
|
Client_Privacy_Violation | /apps/web/src/app/tools/access-intelligence/password-health-members.component.html: 51 |
|
Client_Privacy_Violation | /apps/web/src/app/tools/access-intelligence/password-health-members.component.html: 46 |
|
Client_Privacy_Violation | /apps/web/src/app/tools/access-intelligence/password-health-members.component.html: 41 |
|
Client_Privacy_Violation | /apps/web/src/app/tools/access-intelligence/password-health-members.component.html: 46 |
|
Client_Privacy_Violation | /apps/browser/src/autofill/popup/settings/autofill-v1.component.ts: 101 |
|
Client_Privacy_Violation | /apps/browser/src/vault/popup/components/vault/password-history.component.html: 18 |
|
Client_Privacy_Violation | /apps/browser/src/vault/popup/components/vault/password-history.component.html: 18 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 190 |
|
Unpinned Actions Full Length Commit SHA | /version-auto-bump.yml: 20 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1292 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 246 |
|
Unpinned Actions Full Length Commit SHA | /brew-bump-desktop.yml: 25 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 161 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1338 |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 366 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 296 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 498 |
|
Unpinned Actions Full Length Commit SHA | /retrieve-current-desktop-rollout.yml: 22 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 195 |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 34 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 47 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 244 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 341 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 140 |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 40 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 266 |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 407 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 514 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 180 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 179 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 81 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 287 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 186 |
|
Unpinned Actions Full Length Commit SHA | /staged-rollout-desktop.yml: 28 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 890 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 103 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 358 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 121 |
|
Unpinned Actions Full Length Commit SHA | /publish-web.yml: 43 |
|
Unpinned Actions Full Length Commit SHA | /build-cli.yml: 404 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 296 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 200 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 522 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 193 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 506 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 140 |
|
Unpinned Actions Full Length Commit SHA | /brew-bump-desktop.yml: 25 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 186 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 296 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 200 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 47 |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 40 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 341 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 498 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 890 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 506 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 121 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1338 |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 407 |
|
Unpinned Actions Full Length Commit SHA | /build-desktop.yml: 1292 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 179 |
|
Unpinned Actions Full Length Commit SHA | /staged-rollout-desktop.yml: 28 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 190 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 161 |
|
Unpinned Actions Full Length Commit SHA | /build-browser.yml: 366 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 296 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 81 |
|
Unpinned Actions Full Length Commit SHA | /retrieve-current-desktop-rollout.yml: 22 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 180 |
|
Unpinned Actions Full Length Commit SHA | /publish-web.yml: 43 |
|
Unpinned Actions Full Length Commit SHA | /build-web.yml: 266 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 193 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 522 |
|
Unpinned Actions Full Length Commit SHA | /crowdin-pull.yml: 34 |
|
Unpinned Actions Full Length Commit SHA | /build-cli.yml: 404 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 358 |
|
Unpinned Actions Full Length Commit SHA | /version-auto-bump.yml: 20 |
|
Unpinned Actions Full Length Commit SHA | /publish-cli.yml: 103 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 246 |
|
Unpinned Actions Full Length Commit SHA | /version-bump.yml: 514 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 195 |
|
Unpinned Actions Full Length Commit SHA | /publish-desktop.yml: 244 |
|
Use_of_Broken_or_Risky_Cryptographic_Algorithm | /libs/common/src/platform/services/sdk/default-sdk.service.ts: 155 |
|
Use_of_Broken_or_Risky_Cryptographic_Algorithm | /libs/common/src/platform/services/sdk/default-sdk.service.ts: 172 |
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
đ What if we don't consider just betas? Is the naming of "prerelease" more appropriate? Do we think these need to be enumerated?
đ What if we don't consider just betas? Is the naming of "prerelease" more appropriate? Do we think these need to be enumerated?
Addressed with 3427ea7 (#11605)
đ¤ I see that there aren't any tests for api.service.ts. Should we add that as part of this request?