chore(main): release hve-core 1.1.0#174
Closed
hve-core-release-please[bot] wants to merge 1 commit intomainfrom
Closed
chore(main): release hve-core 1.1.0#174hve-core-release-please[bot] wants to merge 1 commit intomainfrom
hve-core-release-please[bot] wants to merge 1 commit intomainfrom
Conversation
hve-core-release-please
bot
added
the
autorelease: pending
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
WilliamBerryiii
approved these changes
Jan 14, 2026
hve-core-release-please
bot
force-pushed
the
release-please--branches--main--components--hve-core
branch
5 times, most recently
from
7cb06da to
dd5deca
Compare
hve-core-release-please
bot
force-pushed
the
release-please--branches--main--components--hve-core
branch
from
dd5deca to
0fa157c
Compare
This was referenced Feb 13, 2026
WilliamBerryiii
added a commit
that referenced
this pull request
Feb 13, 2026
…eation (#511) ## Description Removed a commit-message guard on the release-please job in the main branch workflow that prevented tag and release creation when release PR merges landed. Release-please v4 handles `chore`-type commits natively, making the guard unnecessary and harmful. - fix(workflows): removed the `if` condition on the `release-please` job in `main.yml` that skipped execution when the head commit started with `chore(main): release`, allowing `createReleases()` to run on release PR merges - docs(architecture): updated `docs/architecture/workflows.md` to explain that release-please v4 handles chore commits natively and removed the stale "(skipped on release commits)" note from the Main Branch Jobs table ## Related Issue(s) Fixes #510 ## Type of Change Select all that apply: **Code & Documentation:** - [x] Bug fix (non-breaking change fixing an issue) - [ ] New feature (non-breaking change adding functionality) - [ ] Breaking change (fix or feature causing existing functionality to change) - [x] Documentation update **Infrastructure & Configuration:** - [x] GitHub Actions workflow - [ ] Linting configuration (markdown, PowerShell, etc.) - [ ] Security configuration - [ ] DevContainer configuration - [ ] Dependency update **AI Artifacts:** - [ ] Reviewed contribution with `prompt-builder` agent and addressed all feedback - [ ] Copilot instructions (`.github/instructions/*.instructions.md`) - [ ] Copilot prompt (`.github/prompts/*.prompt.md`) - [ ] Copilot agent (`.github/agents/*.agent.md`) - [ ] Copilot skill (`.github/skills/*/SKILL.md`) > **Note for AI Artifact Contributors**: > > - **Agents**: Research, indexing/referencing other project (using standard VS Code GitHub Copilot/MCP tools), planning, and general implementation agents likely already exist. Review `.github/agents/` before creating new ones. > - **Skills**: Must include both bash and PowerShell scripts. See [Skills](../docs/contributing/skills.md). > - **Model Versions**: Only contributions targeting the **latest Anthropic and OpenAI models** will be accepted. Older model versions (e.g., GPT-3.5, Claude 3) will be rejected. > - See [Agents Not Accepted](../docs/contributing/custom-agents.md#agents-not-accepted) and [Model Version Requirements](../docs/contributing/ai-artifacts-common.md#model-version-requirements). **Other:** - [ ] Script/automation (`.ps1`, `.sh`, `.py`) - [ ] Other (please describe): ## Testing - Ran `npm run lint:md` with 0 errors on changed files - Ran `npx cspell` with 0 issues on changed files - Validated all 24 workflow files with `actionlint` ## Checklist ### Required Checks - [x] Documentation is updated (if applicable) - [x] Files follow existing naming conventions - [x] Changes are backwards compatible (if applicable) - [ ] Tests added for new functionality (if applicable) ### Required Automated Checks The following validation commands must pass before merging: - [x] Markdown linting: `npm run lint:md` - [x] Spell checking: `npm run spell-check` - [ ] Frontmatter validation: `npm run lint:frontmatter` - [ ] Link validation: `npm run lint:md-links` - [ ] PowerShell analysis: `npm run lint:ps` ## Security Considerations <!--⚠️ WARNING: Do not commit sensitive information such as API keys, passwords, or personal data --> - [x] This PR does not contain any sensitive or NDA information - [ ] Any new dependencies have been reviewed for security issues - [ ] Security-related scripts follow the principle of least privilege ## Additional Notes Previously validated in `Azure-Samples/azure-nvidia-robotics-reference-architecture` (PR #175 / issue #174). The guard was originally added for release-please v3 loop prevention, which v4 handles internally by classifying `chore` commits as non-releasable. 🔧 - Generated by Copilot
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
1.1.0 (2026-01-16)
✨ Features
🐛 Bug Fixes
📚 Documentation
🔧 Maintenance
This PR was generated with Release Please. See documentation.