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.

Sign up for GitHub

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

Jump to bottom

Version Packages #3559

Closed
wants to merge 1 commit into from
Closed

Version Packages #3559

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 12, 2024 •
edited
Loading

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]

Minor Changes

  • #3640 c880687 Thanks @steveluscher! - Removed the fees sysvar which has been disabled on the network for a year, and has now been removed from the test validator in Agave 2.0

    % solana feature status JAN1trEUEtZjgXYzNBYHU9DYd7GnThhXfFP7SzPXkPsG
Feature                                      | Status                  | Activation Slot | Description
JAN1trEUEtZjgXYzNBYHU9DYd7GnThhXfFP7SzPXkPsG | active since epoch 483  | 208656004       | disable fees sysvar

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.

  • #3661 29d1e28 Thanks @steveluscher! - Disabled the MaxListenersExceededWarning in Node when creating event targets for internal use

  • 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

  • #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 force-pushed the changeset-release/master branch 17 times, most recently from 8156493 to f67bdc8 Compare November 18, 2024 10:08
@github-actions github-actions bot force-pushed the changeset-release/master branch 13 times, most recently from 09915c8 to cbb2017 Compare November 25, 2024 10:02
@github-actions github-actions bot force-pushed the changeset-release/master branch 26 times, most recently from e5dd0eb to 2458d9b Compare December 11, 2024 08:30
@github-actions github-actions bot force-pushed the changeset-release/master branch from 2458d9b to 214234e Compare December 11, 2024 08:34
@steveluscher steveluscher deleted the branch master December 14, 2024 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@steveluscher