Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: coze-dev/coze-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.3.3
Choose a base ref
...
head repository: coze-dev/coze-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
  • 7 commits
  • 64 files changed
  • 6 contributors

Commits on Jul 8, 2025

  1. Configuration menu
    Copy the full SHA
    5a3001b View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    803c7a4 View commit details
    Browse the repository at this point in the history

Commits on Aug 1, 2025

  1. Configuration menu
    Copy the full SHA
    03314ae View commit details
    Browse the repository at this point in the history

Commits on Aug 7, 2025

  1. Configuration menu
    Copy the full SHA
    064d6bd View commit details
    Browse the repository at this point in the history

Commits on Aug 23, 2025

  1. Configuration menu
    Copy the full SHA
    ffd3528 View commit details
    Browse the repository at this point in the history

Commits on Sep 2, 2025

  1. chore: Potential fix for code scanning alert no. 6: Workflow does not…

    … contain permissions (#122)
    
    Potential fix for
    [https://github.com/coze-dev/coze-java/security/code-scanning/6](https://github.com/coze-dev/coze-java/security/code-scanning/6)
    
    To fix the problem, add an explicit `permissions` block set to the least
    privilege at the job or workflow level.
    - In general, this is best done at the top of the workflow for clarity
    and maintainability.
    - In this workflow, adding `permissions: contents: read` at the root
    level ensures all jobs and steps only receive minimal access to
    repository contents via the `GITHUB_TOKEN`.
    - The block should be inserted between the workflow name and the `on:`
    or after `on:`, before `jobs:`.
    
    
    _Suggested fixes powered by Copilot Autofix. Review carefully before
    merging._
    
    Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
    chyroc and github-advanced-security[bot] authored Sep 2, 2025
    Configuration menu
    Copy the full SHA
    26b79da View commit details
    Browse the repository at this point in the history

Commits on Oct 15, 2025

  1. fix: license (#129)

    dragooncjw authored Oct 15, 2025
    Configuration menu
    Copy the full SHA
    a1dad15 View commit details
    Browse the repository at this point in the history
Loading