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

Version Packages #1

Closed
wants to merge 1 commit into from
Closed

Conversation

github-actions[bot]
Copy link

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@solana/[email protected]

Minor Changes

  • #3564 5af7f20 Thanks @steveluscher! - When the HTTP transport throws an error, you can now access the response headers through e.context.headers. This can be useful, for instance, if the HTTP error is a 429 Rate Limit error, and the response contains a Retry-After header.

    try {
        const { value: latestBlockhash } = await rpc.getLatestBlockhash().send();
    } catch (e) {
        if (isSolanaError(e, SOLANA_ERROR__RPC__TRANSPORT_HTTP_ERROR)) {
            if (e.context.code === 429 /* rate limit error */) {
                const retryAfterHeaderValue = e.context.headers.get('Retry-After');
                if (retryAfterHeaderValue != null) {
                    // ...
                }
            }
        }
    }

Patch Changes

  • #3552 1adf435 Thanks @leantOnSol! - A two-versions-old version of Node LTS is now specified everywhere via the engines field, including the one in the root of the pnpm workspace, and engine-strictness is delegated to the .npmrc files.

  • #3632 704d8a2 Thanks @mcintyre94! - Change data field of transaction message instructions to use ReadonlyUint8Array

@solana/[email protected]

Minor Changes

  • #3564 5af7f20 Thanks @steveluscher! - When the HTTP transport throws an error, you can now access the response headers through e.context.headers. This can be useful, for instance, if the HTTP error is a 429 Rate Limit error, and the response contains a Retry-After header.

    try {
        const { value: latestBlockhash } = await rpc.getLatestBlockhash().send();
    } catch (e) {
        if (isSolanaError(e, SOLANA_ERROR__RPC__TRANSPORT_HTTP_ERROR)) {
            if (e.context.code === 429 /* rate limit error */) {
                const retryAfterHeaderValue = e.context.headers.get('Retry-After');
                if (retryAfterHeaderValue != null) {
                    // ...
                }
            }
        }
    }

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

  • #3552 1adf435 Thanks @leantOnSol! - A two-versions-old version of Node LTS is now specified everywhere via the engines field, including the one in the root of the pnpm workspace, and engine-strictness is delegated to the .npmrc files.

  • Updated dependencies [1adf435, 5af7f20, 704d8a2]:

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

  • #3552 1adf435 Thanks @leantOnSol! - A two-versions-old version of Node LTS is now specified everywhere via the engines field, including the one in the root of the pnpm workspace, and engine-strictness is delegated to the .npmrc files.

  • Updated dependencies [1adf435, 5af7f20, 704d8a2]:

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

  • #3552 1adf435 Thanks @leantOnSol! - A two-versions-old version of Node LTS is now specified everywhere via the engines field, including the one in the root of the pnpm workspace, and engine-strictness is delegated to the .npmrc files.

  • Updated dependencies [1adf435, 5af7f20, 704d8a2]:

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

@solana/[email protected]

Patch Changes

  • #3552 1adf435 Thanks @leantOnSol! - A two-versions-old version of Node LTS is now specified everywhere via the engines field, including the one in the root of the pnpm workspace, and engine-strictness is delegated to the .npmrc files.

@solana/[email protected]

@solana/[email protected]

@solana/[email protected]

@solana/[email protected]

@solana/[email protected]

@github-actions github-actions bot added the stale label Dec 16, 2024
@github-actions github-actions bot closed this Dec 24, 2024
Copy link
Author

github-actions bot commented Jan 7, 2025

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants