| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
This will silence the warning about needing to pin the version in the
Summary Page.
|
|
|
|
| |
This will save around a minute of CI time for each run. Also clean up
build.ps1 by removing unnecessary code.
|
|
|
|
|
|
| |
Default is currently clang 14. GHA images are updated at least once per year, so
we don't need to manually install a newer clang version.
Also remove step for installing clang-13 since it's not needed anymore.
|
|
|
|
|
|
| |
This includes both the `lintpy` make target and for CI. We're actively
trying to reduce our python usage, so this only seems to give warnings
for unimportant things such as exceeding the line after deleting python
code.
|
|
|
|
| |
There are 6 remaining 8.0.x patches, tracked in:
https://github.com/neovim/neovim/issues/5431
|
| |
|
| |
|
|\
| |
| | |
ci: Use ubuntu docker container to build appimage
|
| |
| |
| |
| |
| |
| |
| |
| | |
Switch back to Ubuntu 18.04 for buliding the appimage. This allows for
using the appimage on older systems that do not provide GLIBC_2.29.
Fixes #19711.
Fixes #20113.
|
|/
|
|
|
|
| |
backport-action now uses "v0" tag to point to the latest stable version.
This helps us avoid having to manually bump the version to get bug
fixes.
|
|
|
|
|
|
|
|
| |
Skipping the CI on documentation-only changes is no longer appropriate
as we now rely on CI to test parts of documentation, e.g.
test/functional/lua/help_spec.lua.
Ignore changes in contrib/ as it's for non-essential user contributions
that we don't need to test.
|
| |
|
|
|
|
| |
We only have one Windows release job, so the matrix setup isn't needed.
|
|
|
|
| |
Build tree-sitter parsers for arm64 as well as x86
Check that all created binaries contain both architectures
|
|
|
| |
Primary bug fix is allowing backports with empty PR description.
|
|
|
|
| |
Changing the action version to v1 allows us to automatically get patch
updates as it points to the latest stable version.
|
| |
|
| |
|
|
|
|
|
| |
Treesitter parsers are now a mandatory part of the installation and
should be tested on all platforms. Remove `pending_c_parser` helper.
|
|
|
|
| |
replaces deprecated LGTM workflow:
https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/
|
|
|
|
| |
All steps in lint now do now require a Neovim build.
|
| |
|
|
|
|
|
|
|
| |
lintcfull == lintc + uncrustify
We are already running uncrustify separately so can just run lintc
instead.
|
| |
|
| |
|
| |
|
|
|
|
| |
It was never in action since migrating from travis to github actions.
|
|
|
|
| |
Ubuntu-20.04 ships with GCC 10.3.0, which is enough to avoid #14150
|
|
|
|
|
| |
`ubuntu-18.04` is now deprecated and subject to outages, see
https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/
|
|
|
|
|
| |
- forked winget-pkgs to https://github.com/neovim/winget-pkgs
- key stored in WINGET_TOKEN at https://github.com/neovim/neovim/settings/secrets/actions
- deploy key public key stored at https://github.com/neovim/winget-pkgs/settings/keys
|
|
|
|
| |
We use `cpack` to generate the release tarballs on Linux. Now that we
don't need to bundle `libintl`, we can do the same on macOS.
|
|
|
|
| |
The differences in MacOS releases are smaller since they're now upgraded
yearly, meaning the need to test each version is reduced.
|
|
|
|
| |
Problem: Windows package step failed (silently).
Solution: Make sure to configure cmake before attempting to build the package target.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor `build.ps1` into a more modular design
https://github.com/neovim/neovim/blob/9728f3b558c8cf9bd2bc331de8a5cc80ba0d3797/.github/workflows/ci.yml#L283-L296
- Separate CI steps.
- Remove unneeded code related to setting up CMake.
- Use parallel/incremental builds.
- Fix github's cache.
- Clear the way for the possibility of replacing this file with a cmake-preset:
https://github.com/neovim/neovim/pull/19128
|
|
|
|
|
|
| |
It's a leftover artifact that currently just acts as an unnecessary
intermediary script that calls the Makefile. It can be replaced by just
calling the Makefile directly.
|
|
|
|
|
|
| |
Our previous mangling of gettext broke the `HAVE_WORKING_LIBINTL` test
because it prevented CMake from finding `libintl.h`. Let's fix that by
linking Gettext's `include` directory into `/usr/local` too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Dirs "config", "packaging", and "third-party" are all closely related
but this is not obvious from the layout. This adds friction for new
contributors.
Solution:
- rename config/ to cmake.config/
- rename test/config/ to test/cmakeconfig/ because it is used in Lua
tests: require('test.cmakeconfig.paths').
- rename packaging/ to cmake.packaging/
- rename third-party/ to cmake.deps/ (parallel with .deps/)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After some tweaks to our dep builds, we can now build a universal binary
for macOS by using `CMAKE_OSX_ARCHITECTURES`. So, let's do that. This
requires a number of additional changes:
1. We need to build on macOS 11, since earlier versions do not support
building universal (M1 + Intel) binaries.
2. We need to provision a universal `libintl`. The linker will look for
an ARM64 version of this library when linking the `nvim` binary.
While we're here:
1. Link statically to `libintl`. This allows to to avoid having to do
any install name rewriting or codesigning to package Neovim.
2. Bump the `MACOSX_DEPLOYMENT_TARGET` to `11`. We're already using a
`libintl` built by Homebrew (through the pre-installed version of
`gettext`), and that is built for macOS 11.
In order to ensure we link to `libintl.a` instead of `libintl.dylib`, we
have to make sure that CMake can't find the latter. This ideally should
be a matter of doing `brew unlink gettext`. However, CMake is too adept
at finding things that Homebrew has installed (even when not linked), so
we have to do a bit more than that. This appears in the additional step
ensuring static linkage to `libintl`.
We end up breaking some Homebrew-installed software in the process, and
some of these software is called during our build (e.g. curl, git,
wget). To avoid any adverse effects, let's just uninstall them.
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The release script bundles a system library (CoreServices) that was
added in #18294, which leads to errors on M1 since the architecture is
different from the Github runner.
Solution:
Skip CoreServices when bundling the libraries (as was done for the
CoreFoundation library that #18294 replaced with CoreServices).
|
|
|
|
|
|
|
|
|
| |
* build: move the logic for linters to cmake
Cmake is our source of truth. We should have as much of our build
process there as possible so everyone can make use of it.
* build: remove redundant check for ninja generator
The minimum cmake version as of writing this is 3.10, which has ninja
support.
|
| |
|
|\
| |
| | |
ci(api-docs): show required changes with color
|
| |
| |
| |
| | |
It makes it easier to see what needs to be changed.
|
|\ \
| | |
| | | |
ci(api-docs): run in drafts as well
|
| | |
| | |
| | |
| | |
| | | |
A contributor should be able to be sure their PR passes the CI before
clicking "Ready for review".
|
|/ /
| |
| |
| | |
This will make it possible to see what needs to be fixed without having
uncrustify installed locally.
|
|/
|
|
|
|
| |
Since we're not running tests or other things that are more sensitive to
changes in the VM environment, use ubuntu-latest to avoid the busy work
of updating the VM image.
|
|\
| |
| | |
ci(api-docs): upgrade to ubuntu 22 and remove conda dependency
|