<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:25:23 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-3070] Github workflow for Stripes and UI releases</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-3070</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Develop and test Github workflow for tagged releases of Stripes and UI modules.   This workflow is slightly different from other branch workflows in that NPM artifacts are deployed to distinct release repositories.    The conditions on which release workflows are triggered are different as well.   Release workflows should be automatically triggered when a specifically formatted Github tag is created.  e.g vX.X.X.&lt;/p&gt;</description>
                <environment></environment>
        <key id="82087">FOLIO-3070</key>
            <summary>Github workflow for Stripes and UI releases</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30">Ankita Sen</assignee>
                                                                <reporter accountid="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                    </labels>
                <created>Tue, 9 Mar 2021 19:43:34 +0000</created>
                <updated>Thu, 26 Aug 2021 04:33:08 +0000</updated>
                            <resolved>Tue, 10 Aug 2021 17:47:23 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                                                            <comment id="196715" author="5f9abc1eb45b2e007453f423" created="Mon, 7 Jun 2021 21:19:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; Issue with Nexus NPM repo has been resolved.  See 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-3192&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-3192&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;allow GitHub actions to upload artifacts to FOLIO Nexus&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-3192
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 for more details.  That&apos;s the good news.  The bad news is the Publish module descriptor step is broken.   It returns an error similar to: &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Error: {&quot;code&quot;:400,&quot;message&quot;:&quot;Failed to decode:Unexpected character (&apos;-&apos; (code 45)) in numeric value: expected digit (0-9) to follow minus sign, for valid numeric value\n at [Source: (String)\&quot;----------------------------806167094178927838742068\r\nContent-Disposition: form-data; name=\&quot;file\&quot;; filename=\&quot;module-descriptor.json\&quot;\r\nContent-Type: application/json\r\n\r\n{\n  \&quot;id\&quot;: \&quot;***_stripes-core-7.2.100093\&quot;,\n  \&quot;name\&quot;: \&quot;The starting point for Stripes applications\&quot;,\n  \&quot;permissionSets\&quot;: [\n    {\n      \&quot;permissionName\&quot;: \&quot;settings.enabled\&quot;,\n      \&quot;displayName\&quot;: \&quot;UI: settings area is enabled\&quot;\n    }\n  ],\n  \&quot;requires\&quot;: [\n    {\n      \&quot;id\&quot;: \&quot;users-bl\&quot;,\n      \&quot;version\&quot;: \&quot;5.0 6.0\&quot;\n    },\n    {\n      \&quot;id\&quot;:\&quot;[truncated 258 chars]; line: 1, column: 3]&quot;}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;ve verified that there is nothing wrong with the module descriptor itself.  I am able to publish to the same folio registry manually.    I think that there &lt;b&gt;may&lt;/b&gt; be something up with the choice of GA module we are using to perform this step.   Perhaps encoding related.   Maybe we need to use a different Action.   If all else fails we might be able to just use &apos;curl&apos;.   In fact that may be a good place to start.   I&apos;ll leave this for you to take a crack at.    You can see my latest progress on the &apos;malc-test&apos; branch of stripes-core.   &lt;/p&gt;

&lt;p&gt;Let&apos;s use this issue for tracking progress on this rather than the umbrella issue.  &lt;/p&gt;</comment>
                                                            <comment id="196718" author="5f9abc1eb45b2e007453f423" created="Tue, 8 Jun 2021 03:29:10 +0000"  >&lt;p&gt;I think I&apos;ve fixed the publish module descriptor step.    Instead of using the &apos;files&apos; parameter of fjogeleit/http-request  we now use &apos;data&apos; with a value that is set from a new read-file step: &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;      - name: Read module descriptor
        if: ${{ env.PUBLISH_MOD_DESCRIPTOR }} &amp;amp;&amp;amp; contains(github.REF, &apos;master&apos;) || contains(github.REF,&apos;main&apos;) || contains(github.REF,&apos;malc-test&apos;)
        id: moduleDescriptor
        uses: juliangruber/read-file-action@v1
        with:
          path: ./module-descriptor.json

      - name: Publish module descriptor
        if: ${{ env.PUBLISH_MOD_DESCRIPTOR }} &amp;amp;&amp;amp; contains(github.REF, &apos;master&apos;) || contains(github.REF,&apos;main&apos;) || contains(github.REF,&apos;malc-test&apos;)
        id: modDescriptorPost
        uses: fjogeleit/http-request-action@master
        with:
          url: &apos;http://ec2-3-88-110-24.compute-1.amazonaws.com/_/proxy/modules&apos;
          method: &apos;POST&apos;
          contentType: &apos;application/json; charset=utf-8&apos;
          customHeaders: &apos;{ &quot;Accept&quot;: &quot;application/json; charset=utf-8&quot; }&apos;
          data: ${{ steps.moduleDescriptor.outputs.content }}
          username: ${{ secrets.FOLIO_REGISTRY_USERNAME }}
          password: ${{ secrets.FOLIO_REGISTRY_PASSWORD }}

      - name: Show FOLIO registry response
        if: ${{ env.PUBLISH_MOD_DESCRIPTOR }} &amp;amp;&amp;amp; contains(github.REF, &apos;master&apos;) || contains(github.REF,&apos;main&apos;) || contains(github.REF,&apos;malc-test&apos;)
        run: echo &quot;${{ steps.modDescriptorPost.outputs.response }}&quot;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="196720" author="5f9abc1eb45b2e007453f423" created="Tue, 8 Jun 2021 03:33:39 +0000"  >&lt;p&gt;I have one quibble about the conditionals checking for branch names:&lt;/p&gt;

&lt;p&gt;if: ${{ env.PUBLISH_MOD_DESCRIPTOR }} &amp;amp;&amp;amp; contains(github.REF, &apos;master&apos;)...&lt;/p&gt;

&lt;p&gt; If I&apos;m not mistaken, &apos;contains&apos; will match a substring.   If I&apos;m correct about that, branches with names like &apos;my-branch-master&apos; will meet this condition and that would be problematic.  I think we need to tighten that up.   Also, does it make sense to use &apos;$default-branch&apos; instead of specifying &apos;master&apos; or &apos;main&apos;?  &lt;/p&gt;
</comment>
                                                            <comment id="196723" author="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30" created="Thu, 10 Jun 2021 13:09:52 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt;&#160;I fixed a few bugs related to the conditional running of steps. The problem with using $default-branch is that it just has the branch name whereas github.ref produced and string &apos;refs/heads/&amp;lt;branch_name&amp;gt;&apos;. I have another implementation in mind which I will be testing shortly. As of now the Workflow runs without any failures.&lt;/p&gt;</comment>
                                                            <comment id="196725" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 15 Jun 2021 13:08:12 +0000"  >&lt;p&gt;This has been enabled for testing in stripes-core, ui-users, ui-orders, ui-find-plugin-organizations. There&apos;s no rollout yet, see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-3205&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-3205&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;rollout GitHub workflow to the stripes- UI repos&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-3205
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                                                            <comment id="196728" author="5f9abc1eb45b2e007453f423" created="Wed, 16 Jun 2021 19:15:17 +0000"  >&lt;p&gt;This shouldn&apos;t be closed.   It pertains to the workflow needed to generated release artifacts based on release tags.    This particular workflow is similar to the branch/master workflow with the following exceptions:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;FOLIO_NPM_REGISTRY needs to be set to &lt;a href=&quot;https://repository.folio.org/repository/npm-folio/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://repository.folio.org/repository/npm-folio/&lt;/a&gt;&apos; by default (or &lt;a href=&quot;https://repository.folio.org/repository/npm-folio-test/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://repository.folio.org/repository/npm-folio-test/&lt;/a&gt; for testing).&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;It should be automatically triggered when a git tag with the following regular expression format is pushed to the repo - &apos;^v\d+\.\d+\.\d+$&apos;.  e.g. v1.2.3&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The Jenkins release pipeline also does an okapi dependency check.   &lt;a href=&quot;https://github.com/folio-org/jenkins-pipeline-libs/blob/master/vars/okapiModDepCheck.groovy&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/jenkins-pipeline-libs/blob/master/vars/okapiModDepCheck.groovy&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="196730" author="5f9abc1eb45b2e007453f423" created="Wed, 16 Jun 2021 19:16:15 +0000"  >&lt;p&gt;I&apos;ve re-opened this issue. &lt;/p&gt;</comment>
                                                            <comment id="196732" author="5f9abc1eb45b2e007453f423" created="Thu, 15 Jul 2021 02:32:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; I took a look at the release workflow at &lt;a href=&quot;https://github.com/folio-org/ui-users/blob/FOLIO-3067-Ankita/.github/workflows/buildnpmRelease.yml&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-users/blob/FOLIO-3067-Ankita/.github/workflows/buildnpmRelease.yml&lt;/a&gt; and I think the issue that easily stands out is that the env.OKAPI_PULL registry url is incorrect.  &lt;/p&gt;

&lt;p&gt;It&apos;s currently set to: &lt;br/&gt;
&apos;&lt;/p&gt;
{ &quot;urls&quot; : [ &quot;https://repository.folio.org/repository/npm-folio-test/&quot; ] }
&lt;p&gt;&apos; - &lt;br/&gt;
which is an NPM registry.  You want Okapi to actually pull from a module descriptor registry. The correct URL is: &apos;https://folio-registry.folio-dev.folio.org&apos;.  &lt;/p&gt;

&lt;p&gt;Let&apos;s make that change and see where we end up. &lt;/p&gt;</comment>
                                                            <comment id="196734" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 15 Jul 2021 13:43:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-registry.dev.folio.org/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-registry.dev.folio.org/&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="196737" author="5f9abc1eb45b2e007453f423" created="Fri, 23 Jul 2021 20:15:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; - I was able to fix the issue related to pulling module descriptors by adding a &apos;sleep 10&apos; to the step that starts the okapi container (since we want to make sure that Okapi is fully initialized) AND by setting a higher timeout on the step that POSTs the request to pull module descriptors from the FOLIO module descriptor registry to the local Okapi container.    The default timeout for a response is 5 seconds.  I set it to 60 seconds.  It normally doesn&apos;t take 60 seconds to pull all the module descriptors from the module descriptor registry but it takes more than 5 seconds which is why we were getting that &apos;no data received error&apos;.   &lt;/p&gt;

&lt;p&gt;Also,  I changed the order of the steps.  The Okapi dependency check should take place after the module descriptor has been generated but BEFORE we publish artifacts to the NPM and FOLIO MD registry.  &lt;/p&gt;

&lt;p&gt;One other thing I&apos;ll leave to you:    For the release workflow,  the  &apos;Set FOLIO NPM snapshot version&apos; step should be omitted entirely since the release version is just whatever is specified in package.json.   We &lt;b&gt;should&lt;/b&gt;, however, add a step that compares the tag with the version specified in package.json to check if they match.   You&apos;d be surprised how often a mismatch occurs.    The git tag should equal v${package.json version) and the build should fail if it doesn&apos;t match. &lt;/p&gt;</comment>
                                                            <comment id="196740" author="712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30" created="Tue, 3 Aug 2021 10:21:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt;&#160;The release workflow is now ready. The version matching step I did a little differently. I wrote a shell script which reads and extracts the version from the package.json file and then git tags with the extracted version. Below is the script&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
PACKAGE_VERSION=$(cat &lt;span class=&quot;code-keyword&quot;&gt;package&lt;/span&gt;.json | grep version | head -1 | awk -F: &lt;span class=&quot;code-quote&quot;&gt;&apos;{ print $2 }&apos;&lt;/span&gt; | sed &lt;span class=&quot;code-quote&quot;&gt;&apos;s/[\&quot;,]&lt;span class=&quot;code-comment&quot;&gt;//g&apos;&lt;/span&gt; | tr -d &lt;span class=&quot;code-quote&quot;&gt;&apos;[[:space:]]&apos;&lt;/span&gt;) &amp;amp;&amp;amp; git tag v$PACKAGE_VERSION&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;This step fails if there is any type of conflicts such as duplicate tag(it fails now because the tag mentioned in the package.json already exists in the repository of ui-users).&lt;/p&gt;

&lt;p&gt;I have also pushed this workflow to the other three test repositories and the github workflow repository.&lt;/p&gt;</comment>
                                                            <comment id="196742" author="61cd0ca0bce5e00069e98be7" created="Wed, 4 Aug 2021 03:17:38 +0000"  >&lt;p&gt;I did a whitespace cleanup &lt;a href=&quot;https://github.com/folio-org/.github/pull/1&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/1&lt;/a&gt; on the &quot;workflow-templates&quot; area.&lt;/p&gt;

&lt;p&gt;That will help to keep future modifications and copies to be free from clutter.&lt;/p&gt;

&lt;p&gt;However, now wherever this template was copied to, will be out of synchronisation.&lt;/p&gt;</comment>
                                                            <comment id="196744" author="5f9abc1eb45b2e007453f423" created="Wed, 4 Aug 2021 17:45:12 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; I&apos;ve reviewed both the buildNPM and buildnpmRelease workflows on master in the .github repo.   &lt;/p&gt;

&lt;p&gt;1.   Both workflows need some cleanup. e.g remove test branch from conditionals and substitute the NPM and module descriptor test registries with the real values (using vars).  &lt;/p&gt;

&lt;p&gt;2.  In the release workflow,   I don&apos;t understand this test: &lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;PACKAGE_VERSION=$(cat package.json | grep version | head -1 | awk -F: &apos;{ print $2 }&apos; | sed &apos;s/[\&quot;,]//g&apos; | tr -d &apos;[[:space:]]&apos;) &amp;amp;&amp;amp; git tag v$PACKAGE_VERSION
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The tag &lt;b&gt;should&lt;/b&gt; already exist and is what triggers the release workflow.  All we need to do is make sure the version in the package.json matches the git tag we are building in the workflow.   May be I&apos;m not understanding something here.   Also,  you may want to consider getting &apos;version&apos; from package.json using a JSON parser like:  &lt;a href=&quot;https://github.com/marketplace/actions/get-json-property&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/marketplace/actions/get-json-property&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;3.   We really should try to use the OKAPI_IP var in the following steps instead of hard-coding 172.17.0.2.   I don&apos;t think we can rely on this always being the same. &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;      - name: Pull all Module descriptors to local Okapi instance
        if: ${{ env.PUBLISH_MOD_DESCRIPTOR }}
        uses: fjogeleit/http-request-action@master
        with:
          url: http://172.17.0.2:9130/_/proxy/pull/modules
          method: &apos;POST&apos;
          contentType: &apos;application/json; charset=utf-8&apos;
          customHeaders: &apos;{ &quot;Accept&quot;: &quot;application/json; charset=utf-8&quot; }&apos;
          data: ${{ env.OKAPI_PULL }}
          timeout: 60000

      - name: Perform local Okapi dependency check
        if: ${{ env.PUBLISH_MOD_DESCRIPTOR }}
        uses: fjogeleit/http-request-action@master
        with:
          # use in production
          #url: &apos;http://172.17.0.2:9130/_/proxy/modules?preRelease=false&amp;amp;npmSnapshot=false&apos;
          # line below is for testing only --malc
          url: &apos;http://172.17.0.2:9130/_/proxy/modules&apos;
          method: &apos;POST&apos;
          contentType: &apos;application/json; charset=utf-8&apos;
          customHeaders: &apos;{ &quot;Accept&quot;: &quot;application/json; charset=utf-8&quot; }&apos;
          data: ${{ steps.moduleDescriptor.outputs.content }}

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="196748" author="5f9abc1eb45b2e007453f423" created="Wed, 4 Aug 2021 19:15:09 +0000"  >&lt;p&gt;Also, and most importantly, I think,  the release workflow should only be triggered when a tag has been created.  All the conditionals checking for &apos;master&apos; or &apos;main&apos; in the buildNPM workflow shouldn&apos;t be applied to the release workflow.  See this example,  &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/actions/runner/issues/1007#issuecomment-808904408&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/actions/runner/issues/1007#issuecomment-808904408&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="196751" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 5 Aug 2021 13:39:45 +0000"  >&lt;p&gt;Once this is complete we need to sync up with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; regarding rolling this out in individual repos (the goal is to use the new workflow for Kiwi releases).&lt;/p&gt;</comment>
                                                            <comment id="196753" author="5f9abc1eb45b2e007453f423" created="Thu, 5 Aug 2021 19:25:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; class=&quot;user-hover&quot; rel=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; data-account-id=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; accountid=&quot;712020:66ff5e1e-556d-4407-89fd-6ed1fe9b6b30&quot; rel=&quot;noreferrer&quot;&gt;Ankita Sen&lt;/a&gt; - I&apos;ve spent a good chunk of time testing the following condition today and am not able to get it to ever return true.  &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;if: ${{ env.TAG != steps.version.outputs.prop }} 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;ve tried several variations with no success including &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;if: ${{  env.TAG }}  != ${{ steps.version.outputs.prop }}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;You can see an example here:  &lt;a href=&quot;https://github.com/folio-org/ga-test/runs/3255673370?check_suite_focus=true&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ga-test/runs/3255673370?check_suite_focus=true&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feel free to mess around with this in the ga-test repo.  My work is on the &apos;v1.2&apos; branch.  &lt;/p&gt;</comment>
                                                            <comment id="196755" author="61cd0ca0bce5e00069e98be7" created="Fri, 6 Aug 2021 05:01:51 +0000"  >&lt;p&gt;Hooray. I too spent some workflow stuggle time. Mine finally yielded greenness.&lt;/p&gt;

&lt;p&gt;Use the &quot;id&quot; of the relevant step, and use the &quot;if: ${{ ...&quot;&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;if: ${{ env.TAG_VERSION != steps.package_version.outputs.prop }}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="196758" author="5f9abc1eb45b2e007453f423" created="Fri, 6 Aug 2021 12:49:58 +0000"  >&lt;p&gt;Gah!! Another stupid mistake on my part getting the id wrong.  Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="196761" author="5f9abc1eb45b2e007453f423" created="Tue, 10 Aug 2021 17:47:23 +0000"  >&lt;p&gt;I&apos;m closing this issue since we are done with the development of the release workflow.   Roll-out of the new workflows can be tracked in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-3067&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-3067&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Replace Jenkins UI and Stripes CI pipelines with Github Action pipelines&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium&quot; /&gt;
            FOLIO-3067
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-3205&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-3205&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;rollout GitHub workflow to the stripes- UI repos&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-3205
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="82084">FOLIO-3067</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="82097">FOLIO-3192</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="82191">FOLIO-3263</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="82121">FOLIO-3270</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10155"><![CDATA[FOLIO DevOps]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02gli:o</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="388">DevOps Sprint 120</customfieldvalue>
    <customfieldvalue id="1830">DevOps Sprint 116</customfieldvalue>
    <customfieldvalue id="1992">DevOps Sprint 114</customfieldvalue>
    <customfieldvalue id="1993">DevOps Sprint 115</customfieldvalue>
    <customfieldvalue id="954">DevOps Sprint 110</customfieldvalue>
    <customfieldvalue id="1994">DevOps Sprint 117</customfieldvalue>
    <customfieldvalue id="955">DevOps Sprint 111</customfieldvalue>
    <customfieldvalue id="1995">DevOps Sprint 118</customfieldvalue>
    <customfieldvalue id="956">DevOps Sprint 112</customfieldvalue>
    <customfieldvalue id="1996">DevOps Sprint 119</customfieldvalue>
    <customfieldvalue id="957">DevOps Sprint 113</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 10 Jun 2021 13:09:52 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>