copilot-session-usage 0.6.3__tar.gz → 0.6.4__tar.gz

{copilot_session_usage-0.6.3 → copilot_session_usage-0.6.4}/.github/skills/gh-release-notes/SKILL.md

@@ -242,10 +242,15 @@ This release primarily includes updates to the knowledge base documentation and
 When this skill is invoked by a CI job with an explicit output-file request:
 
 - Honor the requested tag range and repository path exactly.
-- Write the final Markdown directly to the requested output file using the file-writing tool.
+- Treat the requested output file as mandatory. Writing it is the only successful completion condition.
+- Use the `create` file tool when the requested file does not exist, or the `edit` file tool when it already exists.
+- After writing, use the `read` file tool to verify that the requested file exists and contains the final release-note Markdown.
 - Do not modify, commit, or push any other repository files.
 - The output file must contain only the final release-note Markdown, without an explanation, title heading, or code fence.
-- The caller may discard the Copilot response stream after the file is written; never use that stream as the release body.
+- The first line must be exactly one of: `## New Features`, `## Enhancements`, `## Bug Fixes`, `## Breaking Changes`, `## Examples`, `## Documentation`, `**Maintenance**`, `**Documentation**`, or `**Internal**`.
+- Do not write a preamble, title, code fence, or explanatory text before the first release-note section or fallback label.
+- Never use the Copilot response stream as output. The caller may discard it after the file is written.
+- Do not report the release notes only in the response. If the file cannot be written or verified, the task has failed.
 - Preserve the user-impact categories, examples, breaking-change detection, and public documentation links described above.
 
 ## How to Use This Skill in a Session

{copilot_session_usage-0.6.3 → copilot_session_usage-0.6.4}/.github/workflows/release.yml

@@ -145,7 +145,7 @@ jobs:
 
           Generate the final release notes for ${TARGET_TAG}, covering the actual changes from ${PREVIOUS_TAG} to ${TARGET_TAG} in ${GITHUB_WORKSPACE}.
 
-          Follow the skill's diff-based analysis process. Include only changes with a proven user-facing consequence; exclude CI, workflows, release automation, internal skills, guidelines, tests, file lists, and other repository housekeeping unless the diff proves direct product impact. If there is no product impact, write exactly this fallback block and no other wording: **Maintenance** followed by a blank line and This release primarily includes updates to the knowledge base documentation and internal repository structure. No changes to the core product functionality or user-facing features. Write the final release-note Markdown directly to ${output_file} in the current workspace using the file-writing tool. Do not put the release notes in your response because the response stream is discarded. Do not modify, commit, or push any other repository files."
+          Follow the skill's diff-based analysis process. Include only changes with a proven user-facing consequence; exclude CI, workflows, release automation, internal skills, guidelines, tests, file lists, and other repository housekeeping unless the diff proves direct product impact. If there is no product impact, write exactly this fallback block and no other wording: **Maintenance** followed by a blank line and This release primarily includes updates to the knowledge base documentation and internal repository structure. No changes to the core product functionality or user-facing features. Writing the final release-note Markdown to ${output_file} is mandatory: use the create or edit file tool, then read the file to verify that it exists and contains the final notes. The first line of the file must be exactly one of `## New Features`, `## Enhancements`, `## Bug Fixes`, `## Breaking Changes`, `## Examples`, `## Documentation`, `**Maintenance**`, `**Documentation**`, or `**Internal**`; do not write a preamble, title, or code fence. Do not return the release notes in your response; the response is discarded. Do not modify, commit, or push any other repository files."
 
           gh copilot -- \
             --prompt "$prompt" \
@@ -164,7 +164,7 @@ jobs:
             > /dev/null
 
           if [[ ! -s "$output_file" ]]; then
-            echo "::error::The gh-release-notes skill did not create $output_file."
+            echo "::error::The gh-release-notes skill did not create the mandatory $output_file."
             exit 1
           fi
 

{copilot_session_usage-0.6.3 → copilot_session_usage-0.6.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: copilot-session-usage
-Version: 0.6.3
+Version: 0.6.4
 Summary: Usage and cost analytics for GitHub Copilot and Copilot-CLI session logs
 Project-URL: Homepage, https://github.com/gsemet/copilot-session-usage
 Project-URL: Documentation, https://copilot-session-usage.readthedocs.io/en/stable/

copilot_session_usage-0.6.4/knowledge/findings/2026.07.24-15.01-actions-token-cannot-create-pr.md

@@ -0,0 +1,31 @@
+---
+type: Finding
+title: Repository Actions policy blocked the pricing refresh pull request
+description: The scheduled pricing workflow had the required YAML scopes, but
+  the repository Actions policy prevented GITHUB_TOKEN from creating its pull
+  request.
+tags: [github-actions, github-token, pull-request, pricing-refresh]
+timestamp: 2026-07-24T15:01:41Z
+confidence: high
+context: >-
+  Investigated scheduled run 30069600604 for gsemet/copilot-session-usage at
+  commit 8ff2944b0d89d7afc4d4705e2476494949347b99 using gh CLI and the local
+  checkout. The workflow declares contents: write and pull-requests: write;
+  the repository API reported default_workflow_permissions=read and
+  can_approve_pull_request_reviews=false.
+links: []
+backlinks: []
+---
+
+Run `30069600604` completed pricing refresh and branch synchronization, then
+failed only when `peter-evans/create-pull-request@v7` attempted to create the
+pull request. GitHub reported: “GitHub Actions is not permitted to create or
+approve pull requests.” The repository allows pull request creation generally
+(`pull_request_creation_policy=all`) and no automation pull request existed.
+
+This means the workflow-level `pull-requests: write` declaration is not enough
+when the repository-level “Allow GitHub Actions to create and approve pull
+requests” policy is disabled. The scheduler needs that repository policy enabled
+or a separately authorized GitHub App/PAT supplied as the action token. This
+finding was verified against the failed run and current repository API settings;
+it does not establish whether an organization policy also constrains the setting.

{copilot_session_usage-0.6.3 → copilot_session_usage-0.6.4}/knowledge/findings/index.md

@@ -7,5 +7,6 @@ Belongs to the Storage layer. Findings are promoted into Concepts or Structures
 
 - [cache_write approximated via fresh_input — matches AIC panel exactly](2026.07.02-23.00-cache-write-approximation.md) — VS Code JSONL logs and agent-traces.db both lack cache_creation token counts. Approximating cache_creation as fresh_input = inputTokens - cachedTokens and billing only the incremental delta (cache_write - input) / 1M produces an exact match to the VS Code AIC panel. Implemented in estimate_cost since v0.3.  [Finding]
 - [Release-note generation reported maintainer changes as user-facing features](2026.07.13-14.27-release-notes-overreported-maintainer-changes.md) — The generated v0.6.1 draft release notes described contributor guidelines, project metadata, and file counts instead of observable product changes.  [Finding]
+- [Repository Actions policy blocked the pricing refresh pull request](2026.07.24-15.01-actions-token-cannot-create-pr.md) — The scheduled pricing workflow had the required YAML scopes, but the repository Actions policy prevented GITHUB_TOKEN from creating its pull request.  [Finding]
 - [Subagent Logs Use runSubagent Prefix](2026.07.02-00.00-subagent-logs-runsubagent-prefix.md) — Subagent activity is recorded in separate JSONL files prefixed with "runSubagent-" inside the session debug-logs directory.  [Finding]
 - [title-*.jsonl adds 1 LLM call and its tokens to tool totals; VS Code panel excludes it](2026.07.02-22.00-title-generation-not-counted-as-model-turn.md) — The VS Code Agent Debug panel "Model Turns" counter excludes title-generation calls. copilot-session-usage counts them. The delta is exactly the title-*.jsonl file's token counts.  [Finding]

copilot_session_usage-0.6.4/src/copilot_session_usage/data/models-and-pricing.lock

@@ -0,0 +1,7 @@
+{
+  "_captured": "2026-07-26T05:42:09.875668+00:00",
+  "_source": "https://raw.githubusercontent.com/github/docs/main/data/tables/copilot/models-and-pricing.yml",
+  "_yaml_path": "/home/runner/work/copilot-session-usage/copilot-session-usage/src/copilot_session_usage/data/models-and-pricing.yml",
+  "model_count": 35,
+  "checksum": "1ea4480ea55b34f4"
+}

{copilot_session_usage-0.6.3 → copilot_session_usage-0.6.4}/src/copilot_session_usage/data/models-and-pricing.yml

@@ -231,6 +231,15 @@
   output: $25.00
   cache_write: $6.25
 
+- model: Claude Opus 5
+  provider: anthropic
+  release_status: GA
+  category: Powerful
+  input: $5.00
+  cached_input: $0.50
+  output: $25.00
+  cache_write: $6.25
+
 - model: Claude Sonnet 5[^sonnet-5-promo]
   provider: anthropic
   release_status: GA
@@ -309,6 +318,16 @@
   cached_input: $0.15
   output: $9.00
 
+- model: 'Gemini 3.6 Flash'
+  provider: google
+  release_status: GA
+  category: Versatile
+  threshold: 'Not applicable'
+  tier: 'Default'
+  input: $1.50
+  cached_input: $0.15
+  output: $7.50
+
 # Microsoft
 - model: 'MAI-Code-1-Flash'
   provider: microsoft

copilot_session_usage-0.6.3/src/copilot_session_usage/data/models-and-pricing.lock

@@ -1,7 +0,0 @@
-{
-  "_captured": "2026-07-10T07:30:47.222629+00:00",
-  "_source": "https://raw.githubusercontent.com/github/docs/main/data/tables/copilot/models-and-pricing.yml",
-  "_yaml_path": "/Users/az02065/Projects/DevTools/copilot-session-usage/src/copilot_session_usage/data/models-and-pricing.yml",
-  "model_count": 33,
-  "checksum": "7bae47530bf10fd2"
-}