Skip to content

Comments

feat(ci): update dev build#178

Merged
ionmincu merged 1 commit intomainfrom
feat/ci_update_dev_publish
Feb 20, 2026
Merged

feat(ci): update dev build#178
ionmincu merged 1 commit intomainfrom
feat/ci_update_dev_publish

Conversation

@ionmincu
Copy link
Collaborator

@ionmincu ionmincu commented Feb 20, 2026

Description

update dev build pipeline

Development Package

  • Use uipath pack --nolock to get the latest dev build from this PR (requires version range).
  • Add this package as a dependency in your pyproject.toml:
[project]
dependencies = [
  # Exact version:
  "uipath-mcp==0.1.0.dev1001780260",

  # Any version from PR
  "uipath-mcp>=0.1.0.dev1001780000,<0.1.0.dev1001790000"
]

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath-mcp = { index = "testpypi" }

[tool.uv]
override-dependencies = [
    "uipath-mcp>=0.1.0.dev1001780000,<0.1.0.dev1001790000",
]

@ionmincu ionmincu self-assigned this Feb 20, 2026
@ionmincu ionmincu added the build:dev Create a dev build from the pr label Feb 20, 2026
Copilot AI review requested due to automatic review settings February 20, 2026 09:28
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

Updates the dev-build publishing workflow to make PR description updates more reliable by using explicit start/end markers around the “Development Package” instructions.

Changes:

  • Add <!-- DEV_PACKAGE_START --> / <!-- DEV_PACKAGE_END --> markers around the generated PR description snippet.
  • Switch PR-body update logic from header-based replacement to marker-based replacement.
  • Expand the generated dependency instructions to include an uv override-dependencies example.
Comments suppressed due to low confidence (1)

.github/workflows/publish-dev.yml:123

  • The new marker-based replacement only updates the PR body when the new DEV_PACKAGE_START/END markers are already present. For PRs that already have a previously-generated "## Development Package" section (from the old regex) but no markers, this will append a second section on every run. Consider adding a fallback that detects/replaces the legacy section (e.g., the previous '## Development Package...(?=##|$)' regex) when markers are absent, or migrate the existing block by wrapping it with the markers before future updates.
          # Check if markers already exist in the PR description
          $markerPattern = "(?s)$([regex]::Escape($startMarker)).*?$([regex]::Escape($endMarker))"
          if ($currentBody -match $markerPattern) {
            # Replace everything between markers (including markers)
            $newBody = $currentBody -replace $markerPattern, $dependencyMessage
          } else {
            # Append the dependency message to the end of the description
            $newBody = if ($currentBody) { "$currentBody`n`n$dependencyMessage" } else { $dependencyMessage }
          }

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ionmincu ionmincu requested a review from radu-mocanu February 20, 2026 09:31
@ionmincu ionmincu merged commit b43ea06 into main Feb 20, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build:dev Create a dev build from the pr

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants