Welcome to the Bluefly.io code repository. By logging in, you agree to comply with our terms of service and code of conduct.

Skip to content

Verify package publication for v0.1.3 across all modules

Objective

Verify that all Drupal modules published v0.1.3 packages to GitLab Composer Registry successfully.

Prerequisites

  • Tags cleaned up (Issue #3)
  • CI pipelines completed

Verification Steps

  1. Check Package Registry:

    curl -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
  "https://gitlab.bluefly.io/api/v4/projects/524/packages?per_page=100" \
  | jq -r .[] | select(.name | startswith("bluefly/")) | "\(.name) | Version: \(.version)"

  2. Expected Results:

    • 18 packages published with version 0.1.3
    • Package namespace: bluefly/*
    • Published date: after tag creation

  3. Test Installation:

    • Create test composer.json
    • Add GitLab Composer Registry
    • Install a sample package
    • Verify version is 0.1.3

Packages to Verify

  • bluefly/ai_agentic_workflows
  • bluefly/ai_agent_crewai
  • bluefly/ai_agent_huggingface
  • bluefly/ai_agent_marketplace
  • bluefly/ai_agent_orchestra
  • bluefly/ai_agents
  • bluefly/ai_agents_charts
  • bluefly/ai_agents_client
  • bluefly/ai_provider_apple
  • bluefly/ai_provider_langchain
  • bluefly/alternative_services
  • bluefly/api_normalizer
  • bluefly/code_executor
  • bluefly/dita_ccms
  • bluefly/gov_compliance
  • bluefly/llm
  • bluefly/mcp_registry
  • bluefly/recipe_onboarding

Success Criteria

  • All 18 packages show version 0.1.3
  • All packages installable via Composer
  • No pipeline failures
  • Package metadata correct (name, version, namespace)

Troubleshooting

If packages not published:

  1. Check CI pipeline logs
  2. Verify git tags exist
  3. Check CI_COMMIT_TAG extraction
  4. Verify GitLab token permissions

Related