[pull] main from PostgREST:main #22
Open
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
wolfgangwalther
force-pushed
the
main
branch
from
c6c1ccf to
6caaee7
Compare
This is not related to nix tooling anymore, because a github action without any nix tooling is updating this now.
This changes the postgrest-release tool to work with our new workflow. It can be run on main and the v* release branches. When on a release branch, it will bump a patch version and push to that branch only. When on main, it will bump a minor version by default. To bump a major version, pass --major. This first bump will be force-pushed to the v<major> branch. A second bump to the current development version will then be pushed to the main branch. The tool will not tag commits anymore - this happens in CI automatically. References #3113 Resolves #3082
This potentially allows to run the remaining tests in those files in parallel mode. References #1799
Changing the PK here will avoid duplicate conflicts with another test. References #1799
The Accept header is parsed case-insensitively now, introducing proper handling of media types specified in upper- and/or mixed-case. Fixes #3478
Moving values defined with `let` to the function arguments (with defaults) means other consumers of `default.nix` can customize these values. One example is a `flake.nix`, which can then supply the `nixpkgs` input.
The $subject commit broke internal_schema_cache_sleep for other tests. This reverts the order change, but keeps the scaling by x1000 to ms and thus changes other users of this setting to the new scale.
It's very unlikely, but it can (and did) happen that both the server and admin ports have the same number returned from freeport(). This then leads to a situation where PostgREST will accept the same port in both cases, because the host "localhost" will allow binding to ipv4 or ipv6 respectively. This will make the IO tests fail. This change makes sure that the admin port will never be the same as the server port and thus avoids this problem.
This was removed in #2825.
This happens a commit is pushed to main while the pipelines have not finished for the previous commit. In this case the devel-tag pipelines will run concurrently, leading to unpredictable results for the devel release.
This doesn't make sense, because each tag is only pushed when those pipelines have already passed. Thus, we can save time and avoid wasting resources and don't run those again.
Since we're currently on the unstable channel and will likely stay there for a while, let's encode this in the update script. Once we switch back to stable, if we do, we can still adjust it again.
Renovate doesn't seem to pick this up, because it's in a matrix specification.
This is built on macos-14, which is running on new arm based hardware, not the old x86_64 ones.
This should have been x86-64, only x64 is not a thing.
When macos-14 was rolled out libpq was not installed, but by now it is by default. Thus, we don't need to do that, it only creates a warning annotation right now.
This happens in forks.
The new GitHub arm runners are available, so we can use them to build the ubuntu aarch64 binary instead of our custom machine.
Much easier to implement and should be easier to find, too.
This has been replaced by using the SSH key.
This is now possible, after we moved to the ARM build to the GitHub runners.
Apparently the STACK_ROOT has been moved to C:\sr - for unknown reasons, at least to me. This should enable caching again and make the stack on windows builds much faster than recently.
This manager was recently introduced to renovate and is now creating PRs for upper version bounds of our haskell dependencies. We still need to figure out how to deal with those in the best way, but some basic configuration can already be done. Here, we: - disallow any of those updates on the backbranches. - group GHC-provided dependencies together. - group packages from the hasql ecosystem together. - the fuzzyset dependency must be restricted to <0.3 - we know that already and did that on purpose.
This partially reverts commit 5316445.
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )