Skip to content

Non-blocking: api7/apisix-nginx-module has delete-branch-on-merge enabled, so as soon as api7/apisix-nginx-module#136 merges, support-openresty-1.31.8.1 is gone and the git clone -b in build-apisix-runtime.sh fails, which turns every later CI run here red until this line is bumped. Could we switch it to the release tag once #136 is tagged, or leave a tracking issue so it doesn't get lost? #26

Open

Description

@shreemaan-abhishek

Non-blocking: api7/apisix-nginx-module has delete-branch-on-merge enabled, so as soon as api7/apisix-nginx-module#136 merges, support-openresty-1.31.8.1 is gone and the git clone -b in build-apisix-runtime.sh fails, which turns every later CI run here red until this line is bumped. Could we switch it to the release tag once #136 is tagged, or leave a tracking issue so it doesn't get lost?

Originally posted by @nic-6443 in #24 (comment)

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions