"Context access might be invalid" warning thrown for repository variables and secrets

[afefer]

Describe the bug
After upgrading to 0.25.8, a "Context access might be invalid" warning is thrown for all repository variables and secrets in the workflow file. Refreshing the secrets/vars in the extension has no effect.

Expected behavior
Secrets/vars should not throw a "Context access might be invalid" warning.

Screenshots

Extension Version
v0.25.8

Additional context
Add any other context about the problem here.

[aschen-builder]

Also seeing this issue still with the latest release.

Previous issues #47 #61 and #67 stated the issue would be fixed with the next release, but issue continues to persist into release v0.25.8 and the change log seems to make no mention of a fix being deployed.

[moshest]

Any update on this?

[acharyasaagar]

I still see this as well; the extension version is v0.25.8

[evertonspader-tomtom]

Seeing the same here constantly with v0.25.8

[avh03]

Just wanted to confirm that the issue continues to persist in 0.25.8 (and it's feeling really annoying)

[anthony9187]

also seeing this constantly in v0.25.8 with env variables, but not secrets

[mickael-h]

Same here. A bit annoying indeed 👍

[Bohemus307]

Still persists kind of embarrassing for GH

[enriquepevida]

ah, i see this is an actual issue. i was going mad with this. Let´s hope it´s fixed soon.

[felipesu19]

Yep, its a bug. Moved to triage. No ETA on a fix, if someone makes a PR to fix, I'm happy to review it.