Skip to content

Conversation

@pixincreate
Copy link
Owner

@pixincreate pixincreate commented Mar 17, 2025

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Check this: rust-lang/cargo#13115 (comment)
Also check this

❯ rustc --print deployment-target
MACOSX_DEPLOYMENT_TARGET=11.0

we need not explicitly pass the deployment target.

Context

release especially when building for mac failed here.

How did you test it?

release should happen.

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

@pixincreate pixincreate self-assigned this Mar 17, 2025
@pixincreate pixincreate added bug Something isn't working CI CI/CD changes labels Mar 17, 2025
@pixincreate pixincreate requested a review from Copilot March 27, 2025 12:47
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses a bug in the release workflow for macOS by removing an unnecessary deployment target and ensuring the correct artifacts are committed and built. The key changes include:

  • Updating the Git commit command to include Cargo.lock.
  • Correcting the version variable interpolation syntax in the release notes generation step.
  • Changing the cross-compilation linker for aarch64-apple-darwin from gcc to clang.
Comments suppressed due to low confidence (1)

.github/workflows/release.yml:165

  • Ensure that clang is installed and properly configured on the runner for the aarch64-apple-darwin target, as this change may result in build failures if clang is unavailable.
CARGO_TARGET_AARCH64_APPLE_DARWIN_LINKER: clang

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working CI CI/CD changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants