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

chore(deps): bump @vercel/flags from 2.6.3 to 3.1.0 #286

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 30, 2025

Bumps @vercel/flags from 2.6.3 to 3.1.0.

Release notes

Sourced from @​vercel/flags's releases.

@​vercel/flags@​3.1.0

Minor Changes

  • 76feb16: Add mergeProviderData function to @vercel/flags.

    This function allows merging ProviderData from multiple sources.

    This is handy when you declare feature flags in code, and want to extend those definitions with data loaded from your feature flag provider.

    import { verifyAccess, mergeProviderData, type ApiData } from '@vercel/flags';
    import { getProviderData } from '@vercel/flags/next';
    import { NextResponse, type NextRequest } from 'next/server';
    import { getProviderData as getStatsigProviderData } from '@flags-sdk/statsig';
    import * as flagsA from '../../../../flags-a'; // your feature flags file(s)
    import * as flagsB from '../../../../flags-b'; // your feature flags file(s)
    export async function GET(request: NextRequest) {
    const access = await verifyAccess(request.headers.get('Authorization'));
    if (!access) return NextResponse.json(null, { status: 401 });
    const providerData = await mergeProviderData([
    // expose flags declared in code first
    getProviderData({ ...flagsA, ...flagsB }),
    // then enhance them with metadata from your flag provider
    getStatsigProviderData({ consoleApiKey: '', projectId: '' }),
    ]);
    return NextResponse.json<ApiData>(providerData);
    }

Patch Changes

  • 2713ea7: Handle undefined values

    • fix: Fall back to defaultValue when a feature flag returns undefined
    • fix: Throw error when a flag resolves to undefined and no defaultValue is present

    The value undefined can not be serialized so feature flags should never resolve to undefined. Use null instead.

    Fix exports

    • fix: Export Identify and Decide types

@​vercel/flags@​3.0.2

Patch Changes

  • 708d5e2: generatePermutations: infer options of boolean flags

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 30, 2025
Copy link

vercel bot commented Jan 30, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
rust-conveyor-filters ❌ Failed (Inspect) Feb 14, 2025 0:35am

@github-actions github-actions bot force-pushed the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch from 3a599de to 767e219 Compare January 30, 2025 11:20
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch from 767e219 to ccddb99 Compare January 30, 2025 20:30
@github-actions github-actions bot force-pushed the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch from ccddb99 to e99896b Compare January 30, 2025 20:30
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch from e99896b to b53a9e3 Compare January 31, 2025 21:49
Bumps [@vercel/flags](https://github.com/vercel/flags) from 2.6.3 to 3.1.0.
- [Release notes](https://github.com/vercel/flags/releases)
- [Commits](https://github.com/vercel/flags/commits/@vercel/flags@3.1.0)

---
updated-dependencies:
- dependency-name: "@vercel/flags"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch from b53a9e3 to 5857efe Compare February 14, 2025 12:33
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 17, 2025

Superseded by #305.

@dependabot dependabot bot closed this Feb 17, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vercel/flags-3.1.0 branch February 17, 2025 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants