adobe / aio-sdk

Module that contains all the Adobe I/O SDKs
Apache License 2.0
9 stars 12 forks source link

Cannot get the latest release version when running npm install #25

Closed kevinolivar closed 2 years ago

kevinolivar commented 2 years ago

Expected Behaviour

Running the following commands should get the latest release version (4.0.0)

npm install @adobe/aio-sdk --save

or

npm install @adobe/aio-sdk@latest --save

Actual Behaviour

Instead, the 3.0.0 is installed.

Steps to Reproduce

npm uninstall @adobe/aio-sdk --save

and run again, the npm install command.

I've been working with Adobe App Builder and here the package list and versions,

"dependencies": {
    "@adobe/exc-app": "^0.2.21",
    "@adobe/react-spectrum": "^3.4.0",
    "@spectrum-icons/workflow": "^3.2.0",
    "cloudevents": "^4.0.2",
    "core-js": "^3.6.4",
    "flagsmith-nodejs": "^2.3.0",
    "node-fetch": "^2.6.0",
    "perf_hooks": "0.0.1",
    "pretty-ms": "^8.0.0",
    "react": "^16.13.1",
    "react-dom": "^16.13.1",
    "react-error-boundary": "^1.2.5",
    "react-router-dom": "^5.2.0",
    "regenerator-runtime": "^0.13.5",
    "uuid": "^8.0.0"
  },
  "devDependencies": {
    "@babel/core": "^7.8.7",
    "@babel/plugin-transform-react-jsx": "^7.8.3",
    "@babel/polyfill": "^7.8.7",
    "@babel/preset-env": "^7.8.7",
    "@openwhisk/wskdebug": "^1.3.0",
    "@types/jest": "^28.1.4",
    "@types/node": "^18.0.1",
    "@types/node-fetch": "^2.6.2",
    "@typescript-eslint/eslint-plugin": "^5.30.5",
    "@typescript-eslint/parser": "^5.30.5",
    "eslint": "^8.19.0",
    "jest": "^27.2.4",
    "npm-run-all": "^4.1.5",
    "prettier": "^2.7.1",
    "shx": "^0.3.4",
    "ts-jest": "^28.0.5",
    "typescript": "^4.7.4"
  },

Node: v14.18.2 NPM: 6.14.15

shazron commented 2 years ago

It turns out the Github Action workflows for this repo are missing -- those automatically publish when the version is updated. Will fix.

aiojbot commented 2 years ago

JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-1897

shazron commented 2 years ago

@kevinolivar should be fixed now

kevinolivar commented 2 years ago

@shazron yep, just tried and worked :-) Thanks for the prompt reply and fix!