chore(deps): update third_party/ni-apis digest to de7e7d3

[renovate]

This PR contains the following updates:

Package	Update	Change
third_party/ni-apis	digest	6c8178d → de7e7d3

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone US/Central, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Test Results

  120 files  ±0    120 suites  ±0   3m 22s ⏱️ -4s
  249 tests ±0    247 ✅ ±0   2 💤 ±0  0 ❌ ±0 
2 490 runs  ±0  2 460 ✅ ±0  30 💤 ±0  0 ❌ ±0 

Results for commit ad97017. ± Comparison against base commit e863e4d.

♻️ This comment has been updated with latest results.

[dixonjoel]

@jfriedri-ni @bkeryan In this case, we don't need to wait 14 days for ni-apis changes I think. So I'm intending to override the renovate check and squash this. Do you guys agree? Is there a renovate change or exception we need to make to allow not waiting in this scenario?

[jfriedri-ni]

Is there a renovate change or exception we need to make to allow not waiting in this scenario?

We could likely scope the age-rule to package manager categories -- keep Python on the timer but allow git submodules to update at any age.

[dixonjoel]

Is there a renovate change or exception we need to make to allow not waiting in this scenario?

We could likely scope the age-rule to package manager categories -- keep Python on the timer but allow git submodules to update at any age.

Not super familiar with renovate, but would that just be adding a 'minimumReleaseAge' to this rule that's already in place?
"packageRules": [
{
"description": "Update ni-apis on early Monday mornings.",
"matchDepNames": [
"third_party/ni-apis"
],
"extends": [
"schedule:weekly"
]
}
]
I'll take a look at this more closely.

[dixonjoel]

@jfriedri-ni @bkeryan Copilot says I can do this. I think 2 days seems like a good time. Lmk if you want something different.

{
    "$schema": "https://docs.renovatebot.com/renovate-schema.json",
    "extends": [
        "local>ni/python-renovate-config:recommended",
        "local>ni/python-renovate-config//presets/enableGitSubmodules"
    ],
    "packageRules": [
        {
            "description": "Update ni-apis on early Monday mornings.",
            "matchDepNames": [
                "third_party/ni-apis"
            ],
            "extends": [
                "schedule:weekly"
            ],
            "minReleaseAge": "2d"
        }
    ]
}

[dixonjoel]

Well, whatever I did in #292 didn't seem to work. I did check the 'Rebase' box in the PR description and it re-ran the checks. Is there more to do? I also tried to look at the renovate log you get when you click 'Details' on the check, but I couldn't tell from that what might be wrong.

@bkeryan @jfriedri-ni

Oh, nevermind. I guess it also updated to this recent commit 6 hours ago in the process. So I'll check again tomorrow around noon.

ni/ni-apis@de7e7d3

[bkeryan]

Well, whatever I did in #292 didn't seem to work. I did check the 'Rebase' box in the PR description and it re-ran the checks. Is there more to do? I also tried to look at the renovate log you get when you click 'Details' on the check, but I couldn't tell from that what might be wrong.

@bkeryan @jfriedri-ni

Oh, nevermind. I guess it also updated to this recent commit 6 hours ago in the process. So I'll check again tomorrow around noon.

ni/ni-apis@de7e7d3

You should be able to merge this without waiting. renovate/stability-days is not in the ruleset's required checks.

[dixonjoel]

Well, whatever I did in #292 didn't seem to work. I did check the 'Rebase' box in the PR description and it re-ran the checks. Is there more to do? I also tried to look at the renovate log you get when you click 'Details' on the check, but I couldn't tell from that what might be wrong.
@bkeryan @jfriedri-ni
Oh, nevermind. I guess it also updated to this recent commit 6 hours ago in the process. So I'll check again tomorrow around noon.
ni/ni-apis@de7e7d3

You should be able to merge this without waiting. renovate/stability-days is not in the ruleset's required checks.

Good point. I'm still going to wait to see if it goes green to test my changes are working.

[dixonjoel]

Well, whatever I did in #292 didn't seem to work. I did check the 'Rebase' box in the PR description and it re-ran the checks. Is there more to do? I also tried to look at the renovate log you get when you click 'Details' on the check, but I couldn't tell from that what might be wrong.
@bkeryan @jfriedri-ni
Oh, nevermind. I guess it also updated to this recent commit 6 hours ago in the process. So I'll check again tomorrow around noon.
ni/ni-apis@de7e7d3

You should be able to merge this without waiting. renovate/stability-days is not in the ruleset's required checks.

Good point. I'm still going to wait to see if it goes green to test my changes are working.

@bkeryan I'm wondering if this 'weekly' schedule prevents renovate from even checking the stability days except for once a week. So far I haven't gotten it to update the check on this PR in spite of several rebase and dependency dashboard check box attempts. I'm thinking I'll try changing this schedule to, e.g. hourly even if temporary to see if I can get the step to go green. My suspicion is that if we don't change anything, it might go green next Monday.
"packageRules": [
{
"description": "Update ni-apis on early Monday mornings.",
"matchDepNames": [
"third_party/ni-apis"
],
"extends": [
"schedule:weekly"
],
"minimumReleaseAge": "1 day"
}
]