Reconciles develop to master's latest renovate values for deps bumped on the 2.7 line but never back-merged, so the develop->master 2.8 promotion (#10777) doesn't regress them. Done as a value reconcile, not a cherry-pick: several master commits are superseded (5 device-ui bumps, 2 ststm32 bumps), and develop's stale archive/refs/tags/ URL form actually blocked renovate from bumping these (the regex expects archive/<version>.zip). GitHub Actions: - actions/checkout v6 -> v7 (35 refs) - actions/cache v5 -> v6 - actions/github-script v8 -> v9 (3 refs) - actions/stale v10.2.0 -> v10.3.0 Build / platform: - alpine 3.23 -> 3.24 (alpine.Dockerfile) - platformio/ststm32 19.5.0 -> 19.7.0 - platformio/nordicnrf52 10.11.0 -> 10.12.0 Libraries: - Adafruit SSD1306 2.5.16 -> 2.5.17 - SparkFun MMC5983MA v1.1.4 -> v1.1.5 - Sensirion I2C SCD30 1.0.0 -> 1.1.1 - meshtastic esp8266-oled-ssd1306 6bfd1f1 -> 2e26010 Deliberately excluded: - meshtastic/device-ui digest: coupled to firmware protobuf/API and develop has diverged hard (NodeDB v25); left for a separate maintainer bump + visual check. - libpax: develop uses the mverch67 fork (pinned by Arduino-3.x migration #9122), master uses dbinfrago -- a fork divergence, not a version bump; not reconciled. - platform-native digest: develop already at 61067ac (equal to master).
27 lines
978 B
YAML
27 lines
978 B
YAML
name: process stale Issues and PR's
|
|
on:
|
|
schedule:
|
|
- cron: 0 6 * * *
|
|
workflow_dispatch: {}
|
|
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
actions: write
|
|
|
|
jobs:
|
|
stale_issues:
|
|
if: github.repository == 'meshtastic/firmware'
|
|
name: Close Stale Issues
|
|
runs-on: ubuntu-latest
|
|
|
|
steps:
|
|
- name: Stale PR+Issues
|
|
uses: actions/stale@v10.3.0
|
|
with:
|
|
days-before-stale: 45
|
|
stale-issue-message: This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.
|
|
close-issue-message: This issue has not had any comment since the last notice. It has been closed automatically. If this is incorrect, or the issue becomes relevant again, please request that it is reopened.
|
|
exempt-issue-labels: pinned,3.0,triaged,backlog
|
|
exempt-pr-labels: pinned,3.0,triaged,backlog
|