Does meta-openembedded kirkstone branch will have update for NodeJS considering that nodejs 16 is now EOL ? #740
Comments
|
There is no plan. Stable branches typically do not update packages. Its not uncommon for packages to reach EOL will they are present in a Stable branch. If you need a newer version I suggest either including it in your own layer or submit patches to https://git.yoctoproject.org/meta-lts-mixins so a broader community may contribute. Using mickledore may be an option but it will EOL as soon as Nanbield is released. BR, |
|
Thank you very much @akuster for you answer and suggestions |
cheeyanglee
pushed a commit
to cheeyanglee/meta-openembedded
that referenced
this issue
Sep 22, 2023
Changelog:
===========
Added:
-----------
add ${BATS_TEST_TAGS[@]} for querying the tags during a test (openembedded#705)
print tags on failing tests (openembedded#705)
test for negative arguments to --jobs (openembedded#693)
add tests for --formatter cat (openembedded#710)
test coverage in CI (openembedded#718)
Support for rush as alternative to GNU parallel (openembedded#729)
add bats_pipe helper function for run that executes \| as pipes (openembedded#663)
publish docker images to ghcr.io (additionally to Dockerhub) (openembedded#740)
Fixed:
---------
fix run with options overwriting the value of i (openembedded#726, openembedded#727)
fix ${BATS_TEST_NAMES[@]} containing only --tags instead of test name since Bats v1.8.0 (openembedded#705)
fix run --keep-empty-lines counting trailing \n as (empty) new line (openembedded#711)
fix short flag unpacker creating bogus command lines with valued flags (openembedded#732)
fix formatter becoming confused with retries (openembedded#734)
fix --gather-test-outputs-in fails on tests with / (openembedded#735)
fix overriding date breaks --timing (openembedded#736)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does meta-openembedded kirkstone branch will have update for NodeJS considering that nodejs 16 is now EOL (NodeJs Release) ?
What is the plan ?
Should we migrate to another meta-openembedded branch while using meta poky kirkstone branch ?
Thank you for your feedback,
Aurelien BOUIN
The text was updated successfully, but these errors were encountered: