pliancy / intune-node Goto Github PK

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://x-access-token:[secure]@github.com/santese/intune-node.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

• Add functionality to decrypt .intunewin & extract data for win32 app uploads

@santese, thank you for this wonderful library 🙏.

When submitting a LOB app, things are failing on the commit step. I think the problem is in my fileEncryptionInfo. Would you please share the javascript, if you have it, that creates the fileEncryptionInfo? I'd love to reference my code against a working example.

This is my attempt at it, which fails on the commit step.

const originalFileBuffer = fs.readFileSync(originalPath);

const key = crypto.randomBytes(32);
const iv = crypto.randomBytes(16);
const encryptor = crypto.createCipheriv('aes-256-cbc', key, iv);

// readFileSync will return a buffer when no encoding option is supplied
let encrypted = encryptor.update(originalFileBuffer);
encrypted = Buffer.concat([encrypted, encryptor.final()])

const hmacKey = crypto.randomBytes(32);
const hmac = crypto.createHmac('sha256', hmacKey);
hmac.update(encrypted)
const hmacHash = hmac.digest();

let encryptedWithHmac = Buffer.concat([hmacHash, iv, encrypted])
fs.writeFileSync(encryptedPath, encryptedWithHmac)

const encryptionInfo = {
        encryptionKey: key.toString('base64'),
        macKey: hmacKey.toString('base64'),
        initializationVector: iv.toString('base64'),
        mac: hmacHash.toString('base64'),
        profileIdentifier: 'ProfileVersion1',
        fileDigest: crypto.createHash('sha256').update(originalFileBuffer).digest('base64'),
        fileDigestAlgorithm: 'SHA256'
};

console.log("***ENCRYPTION INFO***")
console.log(encryptionInfo)

const originalSize = fs.statSync(originalPath).size;
const encryptedSize =  fs.statSync(encryptedPath).size;

console.log(`Original size ${originalSize} and encrypted size ${encryptedSize}`)

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Fallback to renovate.json file as a preset is deprecated, please use a default.json file instead.

Datasource	Name	Replacement PR?
npm	npm-run-all

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): replace dependency npm-run-all with npm-run-all2 5.0.0
• fix(deps): update all non-major dependencies (@azure/storage-blob, @types/node, @types/qs, node, qs, rimraf, semantic-release, ts-jest, tslib, typedoc, typedoc-plugin-missing-exports, typescript)
• fix(deps): update dependency axios to v1.7.2
• chore(deps): update dependency husky to v9
• chore(deps): update dependency rimraf to v6
• chore(deps): update dependency typedoc-plugin-missing-exports to v3
• chore(deps): update semantic-release monorepo (major) (@semantic-release/github, @semantic-release/npm, semantic-release)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

uploadToAzureBlob function is failing at blockBlobClient.uploadStream(file, bufferSize, 5). I have confirmed all the steps above the uploadStrem() are successful. This is the error message:

TypeError: _this.readable.on is not a function
at /home/??????/node_modules/@azure/storage-blob/src/utils/BufferScheduler.ts:237:21
....
...
at BlockBlobClient.uploadStream (/home/????????/node_modules/@azure/storage-blob/dist/index.js:14813:22)