Bump follow-redirects from 1.14.4 to 1.14.7 in /website #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.14.4 to 1.14.7. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.14.4...v1.14.7) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
|
Superseded by #4. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/website/follow-redirects-1.14.7
branch
vegerot
pushed a commit
that referenced
this pull request
Jan 8, 2024
Currently, the CMake build system supports three modes for quick-lint-js-generate-lex-keyword: 1. quick-lint-js-generate-lex-keyword is built as part of the current build (QUICK_LINT_JS_ENABLE_BUILD_TOOLS is set) 2. quick-lint-js-generate-lex-keyword is imported from a previous build (QUICK_LINT_JS_USE_BUILD_TOOLS is set) 3. quick-lint-js-generate-lex-keyword is not used at all (neither QUICK_LINT_JS_ENABLE_BUILD_TOOLS nor QUICK_LINT_JS_USE_BUILD_TOOLS is set) Supporting option #3 has a few minor pitfalls. Generated code can get out of sync when cross-compiling. Drop support for option #3. In other words, require either QUICK_LINT_JS_ENABLE_BUILD_TOOLS or QUICK_LINT_JS_USE_BUILD_TOOLS. QUICK_LINT_JS_ENABLE_BUILD_TOOLS is what most people will use, and QUICK_LINT_JS_USE_BUILD_TOOLS is what cross-compilers will use. BREAKING CHANGE: Cross compilers should follow https://quick-lint-js.com/contribute/build-from-source/cross-compiling/
vegerot
pushed a commit
that referenced
this pull request
Jan 8, 2024
Linked_Bump_Allocator is coded to align all allocations to 'alignment' (typically 8). This is problematic for a few reasons: 1. 'alignment' is specified as a compile-time template parameter, forcing Linked_Bump_Allocator to be a template. This probably slows down compilation and clutters the header file. (This is the main problem motivating this patch.) 2. Allocations perform run-time alignment anyways, but on the size rather than on the pointer. 3. The forced alignment wastes some space. 4. Linked_Bump_Allocator cannot support overaligned data. (This isn't a problem yet, and I don't forsee this being a real problem. I mention this for completeness.) Teach Linked_Bump_Allocator to align everything according to a run-time alignment. This will let us fix issue #1 later, directly fixes issue #3, and (with some work included in this patch) fixes #4. This patch might have negative performance costs. I did not measure.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps follow-redirects from 1.14.4 to 1.14.7.
Commits
2ede36dRelease version 1.14.7 of the npm package.8b347cbDrop Cookie header across domains.6f5029aRelease version 1.14.6 of the npm package.af706beIgnore null headers.d01ab7aRelease version 1.14.5 of the npm package.40052eaMake compatible with Node 17.86f7572Fix: clear internal timer on request abort to avoid leakage2e1eaf0Keep Authorization header on subdomain redirects.2ad9e82Carry over Host header on relative redirects (#172)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.